SCCM Duplicate System Entries in the Console
If your SCCM console has duplicated System entries in the Console, and you want to find it right? Below is the Query for this issue.
select R.ResourceID,R.ResourceType,R.Name,R.SMSUniqueIdentifier,R.ResourceDomainORWorkgroup,R.Client from SMS_R_System as r full join SMS_R_System as s1 on s1.ResourceId = r.ResourceId full join SMS_R_System as s2 on s2.Name = s1.Name where s1.Name = s2.Name and s1.ResourceId != s2.ResourceId
We can use WMIC tool to run on remote computers and get the client actions as we want
Some examples to trigger SMS/SCCM Client Actions from command line:
Disable Software-Distribution:
WMIC /namespace:\\root\ccm\policy\machine\requestedconfig path ccm_SoftwareDistributionClientConfig CREATE ComponentName="Disable SWDist",Enabled="false",LockSettings="TRUE",PolicySource="local",PolicyVersion="1.0" ,SiteSettingsKey="1" /NOINTERACTIVE
Re-Activate Software-Distribution:
WMIC /namespace:\\root\ccm\policy\machine\requestedconfig path ccm_SoftwareDistributionClientConfig WHERE ComponentName="Disable SWDist" delete /NOINTERACTIVE
Trigger Hardware Inventory:
WMIC /namespace:\\root\ccm path sms_client CALL TriggerSchedule "{00000000-0000-0000-0000-000000000001}" /NOINTERACTIVE
Trigger Software Inventory:
WMIC /namespace:\\root\ccm path sms_client CALL TriggerSchedule "{00000000-0000-0000-0000-000000000002}" /NOINTERACTIVE
Trigger DataDiscoverRecord (DDR) update:
WMIC /namespace:\\root\ccm path sms_client CALL TriggerSchedule "{00000000-0000-0000-0000-000000000003}" /NOINTERACTIVE
Force a FULL HW Inventory on next HW-Inv Schedule:
WMIC /namespace:\\root\ccm\invagt path inventoryActionStatus where InventoryActionID="{00000000-0000-0000-0000-000000000001}" DELETE /NOINTERACTIVE
Repair SMS/SCCM Agent on a remote client:
WMIC /node:%MACHINE% /namespace:\\root\ccm path sms_client CALL RepairClient
Repair a list (all clients listed in clients.txt) of remote SMS/SCCM Agents:
WMIC /node:@clients.txt /namespace:\\root\ccm path sms_client CALL RepairClient
Collections
.SiteID,
Collections.CollectionName,
Collection_Rules.QueryName,
Collection_Rules_SQL.WQL,
Collection_Rules_SQL.SQLFrom
Collections,Collection_Rules, Collection_Rules_SQLWhere
Collections
.CollectionID = Collection_Rules.CollectionIDAND
Collections.CollectionID = Collection_Rules_SQL.CollectionID-------------------1. Most of the tools that were included in the original SMS Console Additions V1.4
2. The ability to see the computer details and security compliance web reports for a single client inside collections
3. A separate drill down for client logs as well as security update client logs.
4. The ability to check the status of an advertisement with a right click from that advertisement In order to get the client and the advertisement web reports to work you must perform the following.
5. Fixed the right click tools on the "collections" that didn't open a CMD window when running. Also fixed the echo so the results now show up in a command window
6. Will detect the version of the tool installed so re-installation of unnecessary files does not occur when new versions are released
7. Now has an entry in Add Remove Programs which enables un-installation of the program
8. No more hard coding of your site code to get scripts and reports to run correctly
For a Copy a Folder
Dim wShell
strComputer = "."
Set objWMIService = GetObject _
("winmgmts:\\" & strComputer & "\root\cimv2:Win32_Process")
'errReturn = objWMIService.Create _
' ("cmd.exe /c md c:\ups", Null, Null, intProcessID)
Set objFSO = CreateObject("Scripting.FileSystemObject")
objFSO.CopyFolder "file://172.20.128.51/sms_uk/Oct 2008\*.*" , "c:\pav\" , OverwriteExisting
Set wShell = CreateObject("WScript.Shell")
'wShell.Run "c:\ups\Election.html"
Const OverwriteExisting = TRUE
-------------------
Thanks,
http://sccm07.blogspot.com/
Select DISTINCT Model0 from Computer_System_DATA
The above one will show all the Models
The below Query will show everything in the Database
Select
* from Computer_system_dataUsing an editor such as Windows Group Policy editor, open a new or existing Group Policy object.
In the Group Policy editor, navigate to Computer Configuration / Administrative Templates / Windows Components / Windows Update, and then open the properties of the setting Specify intranet Microsoft update service location.
Click Enabled.
In the Set the intranet update service for detecting updates: field, specify the name of the software update point server you want to use, and the port. These must match exactly with the server name format and the port being used by the software update point:
If the site is in mixed mode and software updates is using a custom Web site, the port number is likely to be 8530 unless it has been changed.
If your WSUS Setup configured on port 8530 then the below URL will be placed
In the Set the intranet statistics server: field, specify the name of the intranet statistics server you want to use. There are no specific requirements for specifying this server. It does not have to be the same computer as the software update point server, and the format does not have to match if it is the same server.
Assign the Group Policy object to the computers on which you want to install the Configuration Manager client and receive software updates.
In the Configuration Manager console, navigate to System Center Configuration Manager / Site Database / Site Management / <site code> – <site name> / Site Settings / Client Installation Methods.
Right-click Software Update Point Client Installation, and click Properties.
To enable client installation, select the Enable Software Update Point Client Installation check box.
If the client software on the Configuration Manager 2007 site server is a later version than the client version stored on the software update point, the Upgrade Client Package Version dialog box will open. Click Yes to publish the most recent version of the client software to the software update point.
To finish configuring the software update point client installation, click OK.
First command to start with Powershell is
Power Shell Learning Commands:-
dir -RECURSE
`
Start-Transcript filename.txt
stop-Transcript
I will post to continue this article persistently
-----------------------------------------------------------------------------------------------------------------------------------
SQL Query:-->
-----------------------------------------------------------------------------------------------------------------------------------
To know the package Name and ID
SELECT PackageID, Name
FROM dbo.v_Package
-----------------------------------------------------------------------------------------------------------------------------------
-----------------------------------------------------------------------------------------------------------------------------------
SQL Query:-->
If you want to filter with the package ID then modify the Query to
SELECT PackageID, Name
FROM dbo.v_Package
WHERE (PackageID = 'YourPKGID')
-----------------------------------------------------------------------------------------------------------------------------------
-------------------
Thanks,
http://sccm07.blogspot.com/
Select * from pkgservers where NALpath like '%\\retired DP path\DP$'
Select * from pkgstatus where pkgserver like '%\\retired DP path\DP$'
by runing above two commands verifiy that you have got the correct Correpted DP package ID or not. then if you find it you can safly run the below two commands to delete.
Next delete entries from any of the above tables to the invalid dp share.
Delete from pkgservers where NALpath like '%\\retired DP path\DP$'
Delete from pkgstatus where pkgserver like '%\\retired DP path\DP$'
| Log File Name | Description | ||
| CCMSetup.log | Provides information about client-based operating system actions. | ||
| CreateTSMedia.log | Provides information about task sequence media when it is created. This log is generated on the computer running the Configuration Manager 2007 administrator console. | ||
| DriverCatalog.log | Provides information about device drivers that have been imported into the driver catalog. | ||
| MP_ClientIDManager.log | Provides information about the Configuration Manager 2007 management point when it responds to Configuration Manager 2007 client ID requests from boot media or PXE. This log is generated on the Configuration Manager 2007 management point. | ||
| MP_DriverManager.log | Provides information about the Configuration Manager 2007 management point when it responds to a request from the Auto Apply Driver task sequence action. This log is generated on the Configuration Manager 2007 management point. | ||
| MP_Location.log | Provides information about the Configuration Manager 2007 management point when it responds to request state store or release state store requests from the state migration point. This log is generated on the Configuration Manager 2007 management point. | ||
| Pxecontrol.log | Provides information about the PXE Control Manager. | ||
| PXEMsi.log | Provides information about the PXE service point and is generated when the PXE service point site server has been created. | ||
| PXESetup.log | Provides information about the PXE service point and is generated when the PXE service point site server has been created. | ||
| Setupact.log Setupapi.log Setuperr.log | Provide information about Windows Sysprep and setup logs. | ||
| SmpIsapi.log | Provides information about the state migration point Configuration Manager 2007 client request responses. | ||
| Smpmgr.log | Provides information about the results of state migration point health checks and configuration changes. | ||
| SmpMSI.log | Provides information about the state migration point and is generated when the state migration point site server has been created. | ||
| Smsprov.log | Provides information about the SMS provider. | ||
| Smspxe.log | Provides information about the Configuration Manager 2007 PXE service point. | ||
| SMSSMPSetup.log | Provides information about the state migration point and is generated when the state migration point site server has been created. | ||
| Smsts.log | General location for all operating system deployment and task sequence log events.Log file location:· If task sequence completes when running in the full operating system with a Configuration Manager 2007 client installed on the computer: <CCM Install Dir>\logs· If task sequence completes when running in the full operating system with no Configuration Manager 2007 client installed on the computer: %temp%\SMSTSLOG· If task sequence completes when running in WindowsPE: <largest fixed partition>\SMSTSLOG
| ||
| TaskSequenceProvider.log | Provides information about task sequences when they are imported, exported, or edited. | ||
| USMT Log loadstate.log | Provides information about the User State Migration Tool (USMT) regarding the restore of user state data. | ||
| USMT Log scanstate.log | Provides information about the USMT regarding the capture of user state data. |
When using RDP you may not be able to cut and paste information between your local and remote sessions.
Cause:
The rdpclip.exe processing may not be running on the remote system. Alternatively, the clipboard chain may be incomplete.
Workaround:
Restart the rdpclip.exe process on the remote system.
More Information:
The following article has a good article on Clipboard chaining;
http://blogs.msdn.com/ts/archive/2006/11/16/why-does-my-shared-clipboard-not-work-part-1.aspx
The following stack information from the crash dump was what pointed me in the hotfix direction, the bitblt and drvdither calls which resulted in a divide by zero error in the kernel:
+------------+ | | StackLimit = aa1f5000 +------------+ | : | +------------+ | | KernelStack = aa1f85d8 +------------+ /| | | | | : | | | | stack +------------+ growth | | InitialStack = aa1f9000 +------------+ ChildEBP Ret-Addr Called Procedure --------------------------------------------------------------------------- aa1f8984 80596813 nt!KeBugCheck + 14 aa1f89dc 8053d60f nt!Ki386CheckDivideByZeroTrap + 41 aa1f89dc bf903230 nt!KiTrap00 + 83 aa1f8a94 bf81af4d win32k!UMPDDrvDitherColor + 7d aa1f8b24 bf826e70 win32k!bGetRealizedBrush + 2bd aa1f8b3c bf82f869 win32k!pvGetEngRbrush + 1f aa1f8b98 bf805363 win32k!EngBitBlt + 283 aa1f8be8 bf80bd41 win32k!GrePatBltLockedDC + 1ea aa1f8d54 8053c9fa win32k!NtGdiFlushUserBatch + 689 aa1f8d70 aaea754a nt!KiFastCallEntry + ca aa1f8ddc 805411c2 rdbss!RxpWorkerThreadDispatcher + 18a aa1f8de8 00000000 nt!KiThreadStartup + 16 Notes:
References
Debugging Tools – v6.5.3.8:
http://msdl.microsoft.com/download/symbols/debuggers/dbg_x86_6.5.3.8.exe
Kernel Memory Space Analyzer Version 8.1
http://www.microsoft.com/Downloads/details.aspx?FamilyID=e84d3b35-63c3-445b-810d-9fed3fdeb13f&displaylang=en
First Step Guide to Kernel Memory Space Analyzer V8.1 (Kanalyze)
http://download.microsoft.com/download/8/3/5/835efd1b-d801-4aa5-84ab-c4809fb493f4/Kanalyze%20First%20Step%20Guide%20V8.1.ppt
BitBlt
http://msdn.microsoft.com/en-us/library/ms532278(VS.85).aspx
DrvDitherColor
http://msdn.microsoft.com/en-us/library/ms793395.aspx
Debugging Deadlocks (No Ready Threads)
http://msdn.microsoft.com/en-us/library/cc267852.aspx
Error message when you try to print after you install the GDI security update 925902: "Stop 0x0000007F"
http://support.microsoft.com/kb/935843
This is the first in a series of posts containing information on what I consider the building blocks to automate repetitive tasks at the Windows command-line. These components are the for, find, findstr, set, if and echo commands, control files used for data input, combined with errorlevels, command concatenation, nested loops and if/then/else constructs.
Described in this post is the 'for' command, the most important component in command-line automation. This command provides several methods of looping through a list, and running a command against each element in that list. Use the 'for /?' to get Microsoft help on this command.
Using the 'for' command with one of the syntaxes below provides many benefits, including:
You can use the 'for' command to:
Process a set of filenames or string literals
The filenames or literals can either be directly named in a space-separated set, or you can use wildcards to process more than one file. For example:
for %i in (*.txt) do echo %i
for %i in (test1.txt test2.txt) do echo %i
For example, I would use this syntax if I'm trying to:
Quickly execute something against a group of machines, eg ping each machine:
for %i in (server1 server2 server3 server4) do ping -n 1 %i
Process a series of data files that I have created from another process, eg this uses the regview utility to export the registry entries modified by *.pol files into *.txt:
for %i in (*.pol) do regview %i > %i.txt
Quickly execute the same command with a different variable, eg use the setprinter utility to view all levels of configuration for the specified printer (you could also use for /l in this example):
for %i in (0 1 2 3 4 5 6 7 8 9) do setprinter -show \\server\printer %i
Process a set of directories
The directory names can either be directly named in a space-separated set, or you can use wildcards to process more than one directory. For example:
for /d %i in (%windir%\*) do echo %i
for /d %i in (c:\temp c:\windows) do echo %i
I would use this syntax if I'm trying to do something with each top-level directory, for example:
Report or set ACLs:
for /d %i in (%rootDir%\*) do icacls %i /save %~ni.txt
Rename all the top-level directories to start with a new prefix:
for /d %i in (%rootDir%\*) do ren %i New-%~ni
Process the contents of a text file, line by line
The contents of a file – which I usually refer to as a control file – can be read line-by-line and your command would be run once for each line, substituting tokens from the control file. This provides unlimited capability – construct a control file through any means available and you can then process the entries one-by-one and run a command against that entry.
Note that in Vista at least, just a LF is enough to separate the lines, rather than the Windows standard CR+LF.
For example, assuming you have a control file with a list of servers or workstations, you could:
Lookup the IP address of each machine:
for /f %i in (test.txt) do nslookup %i
Ping each machine:
for /f %i in (test.txt) do ping %i
Remote dir of each machine:
for /f %i in (test.txt) do dir \\%i\c$
I use this constantly to run a command against multiple AD objects, machines, printers, or other network devices, whether the command queries or checks something, or makes a change to each device.
Process the results of a command, line by line
The results of almost any command can be used as the looping mechanism for a 'for /f' command, providing an in-memory control file. For example, you could:
Find the local hostname and then nslookup the computer (you could also use %computername% for this):
for /f %i in ('hostname') do nslookup %i
Query the local Active Directory for a list of DCs (server records) and lookup the IP of each DC:
for /f %i in ('dsquery server -o rdn') do nslookup %i
Recursively enumerate a path
It's possible to recursively enumerate files or directories from a specified starting location, passing each to the body of the for loop. This provides a rudimentary search and response facility, allowing you to traverse a tree looking for objects of a particular type – and then execute something for each found.
For example, you could search from the root of C: for *.txt files, and then report the filename and size (you would just use dir /s if all you wanted to do was echo)
for /r c:\ %i in (*.txt) do echo %i %~zi
Step through a sequence of numbers and execute for each
The 'for /l' option allows stepping through a sequence of numbers, passing the number as a parameter to the body of the 'for' loop.
I don't use this method very often, but it would be another method to the setprinter command above:
for /l %i in (1,1,9) do setprinter -show \\server\printer %i
Variable Expansion
When using 'for', 'for /f' and 'for /d' variable references can also be modified to return substrings or additional information. Note that when using 'for /f', most of these only make sense if you are processing lists of files or directories, but if you did have a control file with files/paths variable expansion does work as expected.
This substitution can be very useful, particularly when constructing parameters to pass to the command in the body of the 'for' loop. For Example:
If you had a number of control files that you wanted to process, outputting the results to a same-named log file:
for %i in (c:\temp\*.txt) do echo Do something with %i > %~ni.log
If the output of a previous command wrapped the results in quotes, but you need to append/prepend something else you can easily remove surrounding quotes:
for /f %i in ('echo "c:\windows"') do echo %~i\temp
Given a list of files, echo those that are zero bytes in size:
for %i in (c:\temp\*.txt) do @if %~zi == 0 @echo %i
Given a full path, split into drive, path and filename:
for %i in (c:\windows\temp\test.txt) do echo %~di %~pi %~nxi
Tokens, delimiters and skipping lines
The simple functionality of the 'for /f' command can be extended very easily with three options:
These options can be used individually or as a combination, for example:
Skip the first line of the control file:
for /f "skip=1" %i in (test.txt) do echo %i
Skip the first line, and use comma's as the delimiter:
for /f "skip=1 delims=," %i in (test.txt) do echo %i
Skip the first two lines, use the second token, separated by comma and space:
for /f "skip=2 tokens=2 delims=, " %i in (test.txt) do echo %i
This was a basic overview of the 'for' command, future posts will build on this foundation with multiple commands, error levels, if/then/else statements and nested 'for' loops.
-------------------
Thanks,
http://sccm07.blogspot.com/
Internal DNS in many organisations is usually a little messy and if tasked with cleaning it, my first step would be to identify duplicate records in DNS - either an IP address that is recorded against multiple host names or a host name with multiple host (A) records. Assuming you have a file containing one record per line, this is fairly simple to report on.
The following examples use dnscmd.exe, which assumes Windows 2000/2003 DNS, but you could use any input, as long as it contains a name and an IP.
The two commands:
The first command uses dnscmd to enumerate the records from the root of the test.local zone and exclude aging (dynamic DNS) records. The last find command further filters the output by IP, which can be useful when targeting specific subnets/sites. You might also want to check aging dynamic records instead of static to see how well scavenging is working – if you do, just change the tokens to 1,5 instead of 1,4 (as the aging data is another token separating the name and IP).
The second command:
printer1 3600 A 192.168.10.100 printer2 3600 A 192.168.10.101 printer3 3600 A 192.168.10.100 printer4 3600 A 192.168.10.102 printer5 3600 A 192.168.10.103 printer6 3600 A 192.168.10.100 printer7 3600 A 192.168.10.102 192.168.10.100,3: printer1 3600 A 192.168.10.100 printer3 3600 A 192.168.10.100 printer6 3600 A 192.168.10.100 192.168.10.102,2: printer4 3600 A 192.168.10.102 printer7 3600 A 192.168.10.102 192.168.10.100,3 192.168.10.102,2