SCCM client installed during OSD but does not show up in console until Machine policy action intitiated manually.
Hi everybody We have a new SCCM infrastructure with only one site. We build laptops using SCCM OSD Tasksequence off of a stand alone media and via console as well.All the machines built show up in the console as client not installed but configmgr client is installed during OSD. When a machine is newly imaged and i open up the ConfigMrg Client, in General tab i see all the information but Site Mode shows as unknown. Under the actions tab, there are only four actions - "Machine Policy", "Software updates Deployment evaluation", "Software updates scan" and "User policy retrieval and evaluation" I have checked Clientlocation.log, LocationServices.log,ClientIDManagerStartup.log and other logs (lot of log files missing as well). Not much of help from the logs, the client is able to discover the assigned site and MP as well. If I manually initiate the "Machine policy" action, the actions tab gets populated with rest of the actions. Then manually initiating "Discovery data cycle", hardware inventory and software inventory actions solve the issue and sccm console shows the machine as client installed and active. Does any have any idea on why this is happening ? I have machines that have been already been handed off to users before i witnessed this issue and show as no client in the console. How can i solve this issue on multiple machines ? Please advise.
November 9th, 2010 2:48pm
I woud expect this to correct itself as soon as the machine gets policy. Is the machine showing assigned? John Marcum | http://myitforum.com/cs2/blogs/jmarcum |
November 9th, 2010 3:28pm
Hi John I expect the same behavior as well but for some reason it does not start by itself. And the machine shows as N\A in "Assigned".
November 9th, 2010 4:45pm
Moving this to the OSD forum. Those guys will have better answers. John Marcum | http://myitforum.com/cs2/blogs/jmarcum |
November 9th, 2010 6:33pm