Getting caught by your own permissions!

I have a confession to make. This is pretty embarrassing,and a terrible mistake. Something I’m not too proud to admit even. 🙂  Raise your hand if you have ever tried to replicate content out to a linked deployment share and get continuous failures. It might look something like the following:

The problem is the share is read-only. You might want to confirm that your account has change/full control access to the deploymentshare. This will likely fix this problem, but keep reading…

I’ve even seen errors like “DISM was unable to set the system root (target path) for the Windows PE Image, so the update process cannot continue.” The DISM error is on the computer running MDT, so it doesn’t have anything to do with the remote server. Look for a message that indicates that the image was mounted successfully. Often then “system root” error is caused by antivirus software prventing access to the just-mounted registry files.

If you have confirmed the proper permissions are setup in this scenarios and you’re still having issues, please save yourself some time and reboot the server. This will likely correct the issues described above.

Advertisements

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s