Want to protect your cyber security and still get fast solutions? Ask a secure question today.Go Premium

x
  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 1159
  • Last Modified:

Cannot run EXPLORER.EXE from Domain accounts after sysprep

I am using MDT 2013 & WDS on Server 2012 to deploy Windows7 x64. If I run the Sysprep and Capture task sequence and then deploy the image all domain accounts on the system get the following error when ever EXPLORER.EXE is invoked.

"Windows cannot access the specified device, path, or file. You may not have the appropriate permissions to access the item."

If I skip the capture and just join it to the domain it works fine. I thought that maybe it had something to do with the Default Profile but existing and newly created local accounts do not exhibit this issue.

Our profiles are redirected to the network. I thought maybe that was an issue but we have an older image built and deployed from MDT 2010 on Server 2K8. Deploying the older image from this server works fine deploying that same image from the 2012 server does not.

The only relevant difference I can see is WinPE. The other server runs an older version. The 2012 server is running the MDT 2013 WinPE (Win8).

My next step is to remove the domain join sequence to see if it makes a difference. After that I will figure out how to build an older version of PE for deployment.

Antivirus is not included in the image.

One other oddity is that I have the big red X through the NIC in the tray but the network is fine.

This is so odd.

Any help is greatly appreciated!
0
MarkMelanson
Asked:
MarkMelanson
  • 5
  • 2
1 Solution
 
bbaoIT ConsultantCommented:
just to double check if the source computer (where the image was captured) was in the domain before capturing the image? It should NOT be in the domain. Every new build using or based on the image should join in the domain individually.
0
 
MarkMelansonAuthor Commented:
No. It was never in the domain.

Sorry I failed to mention that.
0
 
bbaoIT ConsultantCommented:
thanks for the clarification.

one more thing. were the image's OS and applications installed and configured using the SAME user account with ADMIN priviligies?
0
Technology Partners: We Want Your Opinion!

We value your feedback.

Take our survey and automatically be enter to win anyone of the following:
Yeti Cooler, Amazon eGift Card, and Movie eGift Card!

 
MarkMelansonAuthor Commented:
Yes. All the installs are automated and run during the task sequence.
0
 
MarkMelansonAuthor Commented:
I am going to re-create the task sequence from scratch.
0
 
MarkMelansonAuthor Commented:
It is a profile issue. I had to delete the older .DAT files. I think USRCLASS.DAT was the culprit.
0
 
MarkMelansonAuthor Commented:
The script below resolved the issue:

@echo off
PUSHD %~DP0
CLS
echo.
echo Deleting NTUSER Junk in Default Profile...
DEL /ah /f C:\users\Default\*.log*
DEL /ah /f C:\users\Default\NTUSER.DAT{*
echo Deleting APPDATA Junk in Default Profile...
del /AH /F C:\Users\default\AppData\Local\Microsoft\Windows\USRCLASS.dat.*
del /AH /F C:\Users\default\AppData\Local\Microsoft\Windows\USRCLASS.dat{*
popd
echo.
echo Done
1

Featured Post

Concerto Cloud for Software Providers & ISVs

Can Concerto Cloud Services help you focus on evolving your application offerings, while delivering the best cloud experience to your customers? From DevOps to revenue models and customer support, the answer is yes!

Learn how Concerto can help you.

  • 5
  • 2
Tackle projects and never again get stuck behind a technical roadblock.
Join Now