myITforum.com Community Forum myITforum.com Community Forum

Home  Forums  Blogs  Live Support chat  Search Articles  Wiki  FAQ  Email Lists  Register  Login  My Profile  Inbox  Address Book  My Subscription  My Forums 

Photo Gallery  Member List  Search  Calendars  FAQ  Ticket List  Log Out

All Forums RSS Feed Subscription:


  


CM Install Start up Script interfering with “Setup Windows and ConfigMgr” Task Sequence

 
View related threads: (in this forum | in all forums)

Logged in as: Guest
  Printable Version
All Forums >> [Management Products] >> System Center Products >> System Center Configuration Manager >> CM Install Start up Script interfering with “Setup Windows and ConfigMgr” Task Sequence Page: [1]
Login
Message << Older Topic   Newer Topic >>
CM Install Start up Script interfering with “Setup Wi... - 10/3/2008 12:47:01 PM   
xneilpetersonx

 

Posts: 154
Score: 1
Joined: 7/18/2006
Status: offline
I’m running into an issue with this Task Sequence and a CM client install/health script that I have running against production machines. They symptoms are a quick blue screen followed by a reboot at the “Setup Windows and ConfigMgr” task.  I’ve been able to get around this on most machines by having the Task Sequence drop the computer account in an OU not tied to the start up script – then later in the task sequence I have a script that moves the computer account to the correct OU. This works great unless the machine account already exists in AD. In this case the account obviously does not move to the “staging OU” and is thus hit again with the battling start up script vs. Task Sequence.

I am imagining that trying to script the movement of these accounts or even the on the fly deletion may be a bit convoluted and before attempting something thought I would ask for alternate opinions.

Thanks
neilp

< Message edited by xneilpetersonx -- 10/3/2008 12:55:22 PM >
Post #: 1
RE: CM Install Start up Script interfering with “Setu... - 10/4/2008 10:56:22 AM   
rbennett806


Posts: 825
Score: 13
Joined: 6/14/2006
Status: offline
So you've basically got a Startup script trying to install/repair/manage the client during the OSD process? While you could script the computer account object moves (you'll need to wait for things to replicate between your DCs after you move it), it might make more sense to maybe go a different route...

If you're using a Startup script, why not code the script to check for a specific file or registry key that you set in your base OS .WIM image? Code it so that if the file/key exists the script doesn't do anything. Then as the last part of your OSD process, have a script remove that file/registry key so that your Startup script will run as expected.

Just my two cents...

(in reply to xneilpetersonx)
Post #: 2
Page:   [1]
All Forums >> [Management Products] >> System Center Products >> System Center Configuration Manager >> CM Install Start up Script interfering with “Setup Windows and ConfigMgr” Task Sequence Page: [1]
Jump to:





New Messages No New Messages
Hot Topic w/ New Messages Hot Topic w/o New Messages
Locked w/ New Messages Locked w/o New Messages
 Post New Thread
 Reply to Message
 Post New Poll
 Submit Vote
 Delete My Own Post
 Delete My Own Thread
 Rate Posts



  
Forum Software © ASPPlayground.NET Advanced Edition 2.4.5 ANSI

0.266