Sunday, October 07, 2012 5:33 AM
I know that this is kinf on an ambiguous questions, but how long does it typically take for a client to be pushed out to a new device.
In my experience it usually takes a couple of hours, however i have 3 new devices that have been online for 2 days now and client haven't been installed yet.
I see those devices under my dynamic collection. I initiated a client install through collection a few times. Don't really see an errors, unless there is somewhere deeper that i have to dig.
Sunday, October 07, 2012 6:04 AM
the best indicator is your own experience, in your own environment, since it varies widely.
take a look at this troubleshooting article, focus on ccm.log on the site server where you pushed from. (or the site server your remote console was connected to, which is where the push comes from)
(Please take a moment to "Vote as Helpful" and/or "Mark as Answer", where applicable.
This helps the community, keeps the forums tidy, and recognises useful contributions. Thanks!)
Sunday, October 07, 2012 3:38 PM
There are really multiple phases to the entire push process that are explained quite well by the KB posted by Don. Typically, the actual "push" portion should only take a couple of minutes (handled by ccm on the site server), followed the "pull" portion (handled by ccmsetup on the client) which I've seen takes anywhere from a couple of minutes to 10-20 minutes depending upon where the client is pulling the other setup files from and how slow the system is. Once installed, the client must discover its site code and MP and then start communicating with the MP which usually takes just a couple of minutes. Just because a client is communicating doesn't mean the console shows this though as collections are not real-time reflections of the database (that's why I recommend using queries or reports to monitor client installation in 2007) and is why you see the process as taking multiple hours when in fact it usually takes 5-10 minutes. These are essentially three distinct phases (maybe even four if you include the console being updated) so you must troubleshoot each one to know where in the process a problem occurred.
Just to reiterate, the kb that Don posted is essentially a great guidebook on troubleshooting the process.
Jason | http://blog.configmgrftw.com
Wednesday, October 10, 2012 1:47 PM
I got it.
Oddly enough it was an issue with IIS
Thanks for your help guys