Month: October 2014

10 #1 best practices for OS Deployment with ConfigMgr 2012 R2

Here’s a quick list of the links from my TechEd Europe session this morning.  More info to follow over the next few weeks! “KISS—start simple, and work your way toward complexity.” – Rob Marshall “Automate process to import drivers and create driver packages.” – Kent Agerlund and “Automate, Automate, Automate. Manually building images is not […]

Some of my Hot Picks for MMS Sessions

There are a ton of great sessions at MMS. Here’s a pic of many of the keywords you’ll find in the session titles: There are a lot of great speakers, and I’ll be sad because I won’t be able to attend all of the sessions (only so many slots in a 3-day conference :(, and […]

Capture Logs from Task Sequence… and then some

As we all know, ConfigMgr OSD deployment process can sometimes be finicky.  Start imaging two identical computers and one might fail while the other is successful.  There could be a number of reasons:DP replication issuesPlanets are not in alignmentNetwork issuesSomeone cut the hard line.  ???Whatever the cause, If the error is at the beginning of the task sequence there is no major downtime but if the error is towards the end, then that 2-3 hour image deployment process could take 4-6 as they start it over again and for what, Adobe Reader didn't install because someone or something updated the DP content?IssueWe typically do not use the “Continue on error” flag in our TS’ because if a particular step fails, it’s difficult for us to know about that fa...

Capture Logs from Task Sequence… and then some

As we all know, ConfigMgr OSD deployment process can sometimes be finicky.  Start imaging two identical computers and one might fail while the other is successful.  There could be a number of reasons:DP replication issuesPlanets are not in alignmentNetwork issuesSomeone cut the hard line.  ???Whatever the cause, If the error is at the beginning of the task sequence there is no major downtime but if the error is towards the end, then that 2-3 hour image deployment process could take 4-6 as they start it over again and for what, Adobe Reader didn't install because someone or something updated the DP content?IssueWe typically do not use the “Continue on error” flag in our TS’ because if a particular step fails, it’s difficult for us to know about that fa...

Capture Logs from Task Sequence… and then some

As we all know, ConfigMgr OSD deployment process can sometimes be finicky.  Start imaging two identical computers and one might fail while the other is successful.  There could be a number of reasons: DP replication issues Planets are not in alignment Network issues Someone cut the hard line.   ??? Whatever the cause, If the error is at the beginning of the task sequence there is no major downtime but if the error is towards the end, then that 2-3 hour image deployment process could take 4-6 as they start it over again and for what, Adobe Reader didn't install because someone or something updated the DP content? Issue We typically do not use the “Continue on error” flag in our TS’ because if a particular step fails, it’s difficult for us to know ...