We have a Windows 7 OS task sequence. Under the Apply Network Settings we had the following Domain OU: LDAP://OU=REMOTE,OU=CC,OU=Desktops,OU=Computers,DC=msds,DC=ACME,DC=com . When we built machines they got placed here. . We then needed to change this to a new location. The new location is: LDAP://OU=CC,OU=Desktops,OU=Computers,DC=msds,DC=ACME,DC=com . The task sequence was saved and a new boot media was created. We build a few more machines and they all still go to the first location. Why? Is this path cached someplace that you need to flush out? .mqh7

are you re-using existing computername/accounts? if the computer account already exists in your AD, then the existing account will be re-used (stays in the current OU)Don

We are not using the same computer accounts. We've run our boot-media CD on many brand new machines that were fresh out of the box and it does not drop them in OU specified in the TS. We also delete machines from the SCCM DB so they are "unknown" computers again and they never show up in the correct OU. Question: Where did you find the information you provided? "if the computer account already exists in your AD, then the existing account will be re-used (stays in the current OU)" Thanks. mqh7

If you immediately built the boot media after saving the task sequence, it's possible that not enough time passed for the task sequence to be updated. By now, it should be fine. To prevent this from happening in the future (if this is actually the cause), you can restart SMS_Distribution_Manager, then watch the status messages for that component to see if the TS was successfully updated. After that, build your media.Nicholas Jones, MCITP | Core Infrastructure Consultant | Sparkhound | https://www.mcpvirtualbusinesscard.com/VBCServer/nicholas.jones/profile

If you immediately built the boot media after saving the task sequence, it's possible that not enough time passed for the task sequence to be updated. By now, it should be fine. To prevent this from happening in the future (if this is actually the cause), you can restart SMS_Distribution_Manager, then watch the status messages for that component to see if the TS was successfully updated. After that, build your media. Nicholas Jones, MCITP | Core Infrastructure Consultant | Sparkhound | https://www.mcpvirtualbusinesscard.com/VBCServer/nicholas.jones/profile I've had this happen before...............