Thursday, June 14, 2012
Tuesday, May 29, 2012
TO fix the SMS client GUID issue
How to fix the SMS
client GUID issue
1.If the client status unknown in the SMS console after
installing the SMS client (make sure that CCM setup.log shows the succeeded
message)
2.Use the psexec tool to login to the machine locally
Usage of the tool
Psexec \\IPadress of the machine (space) cmd
Make sure that open client
id manager startup.log in the client system to observer the changes
Patch of the client id manager startup.log would be
c:\windows\system32\ccm\logs\
Below are the commands you should execute in the PSEXEC tool
a)
net stop ccmexec
b)
del "%windir%\Smscfg.ini"
c)
net start ccmexec
now open “client id
manager startup.log “ in client system and observe the message
Once you identify that you fixed the client guid , open the
sql and check the system status after few minits .
Use below query to
check the same.
SELECT Name0 AS
[Machine Name], User_Name0 AS [User Name],AD_site_name0 as [AD site code]
,creation_date0 as [AD discoverd date],
CASE Active0 WHEN '0' THEN 'InActive' WHEN '1' THEN 'Active' ELSE
'Unknown' END AS [Active Client],
CASE Client0 WHEN '0' THEN 'No' WHEN '1' THEN 'Yes' ELSE 'Unknown' END
AS [Client Status],
CASE obsolete0 WHEN '0' THEN 'No' WHEN '1' THEN 'Yes' ELSE 'Unknown' END
AS [Obsolete Client], DATEDIFF(D,V_GS_WORKSTATION_STATUS.LASTHWSCAN,GETDATE())
AS [HW SCAN DIFFERENCE]
FROM
v_R_System LEFT JOIN
V_GS_WORKSTATION_STATUS ON V_R_SYSTEM.RESOURCEID =
V_GS_WORKSTATION_STATUS.RESOURCEID
WHERE (Name0 IN (
'Systemanem'))
Monday, May 28, 2012
Office 2007 Normal exit error codes - Install failed
Office 2007 Normal error codes - Install failed
Friday, May 25, 2012
SMS/SCCM Sql required query for Daily administration
SQL Query useful for daily administration
http://sms2003-sccm2007.blogspot.in/2008/08/all-sql-queries.html
http://sms2003-sccm2007.blogspot.in/2008/08/all-sql-queries.html
Dcomcnfg - DCOM Settings
Type in the Run command -
“Dcomcnfg”
Go to computer properties and go
to the “Com security “ edit limits in both accordingly ( just add your login id
and your system name and give all the permissions for you and your computer)
this is required incase you unable to connect to SMS console from XP machine
SMS/SCCM Client Install Script automation
1. Create a folder anywhere in same domain and copy the
ccmsetup.exe and psexec.exe to the folder.
2. Create a text file with name computers.txt under C:\ and enter
the system names one by one where you wanted to install the SMS Client.
3. Copy the below script and name it as SCCMClientInstall.vbs
4. Double click the file.
5. Enter the Path of the folder that you created in the first step
and click ok.
6. Enter the Management Point Name in the next input box. (You can
mention any MP name)
7. Check the ccmsetup.log in one machine to verify the client
install.
Subscribe to:
Posts (Atom)
SCCM to Tanium
SCCM transition Options: of course intune otherwise Deployment, Patching - Tanium Image - Tazier Inventory - Tanium Remote Control - Zoom ...
-
When a package is distributed to a PullDP, DistMgr creates a PkgXferMgr job and added to the queue. - PkgXferMgr processes the job and cre...
-
How to fix the SMS client GUID issue 1.If the client status unknown in the SMS console after installing the SMS client (make sure that ...
-
Below is a PowerShell script, this will list WDS Service status against of List of servers. $InPutComputersList = get-content "c:\M...