Solved

Cannot run EXPLORER.EXE from Domain accounts after sysprep

Posted on 2014-02-26
7
1,076 Views
Last Modified: 2014-07-16
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
Comment
Question by:MarkMelanson
[X]
Welcome to Experts Exchange

Add your voice to the tech community where 5M+ people just like you are talking about what matters.

  • Help others & share knowledge
  • Earn cash & points
  • Learn & ask questions
  • 5
  • 2
7 Comments
 
LVL 37

Expert Comment

by:bbao
ID: 39891566
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
 

Author Comment

by:MarkMelanson
ID: 39891596
No. It was never in the domain.

Sorry I failed to mention that.
0
 
LVL 37

Expert Comment

by:bbao
ID: 39891624
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
Office 365 Training for Admins - 7 Day Trial

Learn how to provision tenants, synchronize on-premise Active Directory, implement Single Sign-On, customize Office deployment, and protect your organization with eDiscovery and DLP policies.  Only from Platform Scholar.

 

Author Comment

by:MarkMelanson
ID: 39891833
Yes. All the installs are automated and run during the task sequence.
0
 

Author Comment

by:MarkMelanson
ID: 39894766
I am going to re-create the task sequence from scratch.
0
 

Accepted Solution

by:
MarkMelanson earned 0 total points
ID: 40191077
It is a profile issue. I had to delete the older .DAT files. I think USRCLASS.DAT was the culprit.
0
 

Author Closing Comment

by:MarkMelanson
ID: 40198828
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

Get 15 Days FREE Full-Featured Trial

Benefit from a mission critical IT monitoring with Monitis Premium or get it FREE for your entry level monitoring needs.
-Over 200,000 users
-More than 300,000 websites monitored
-Used in 197 countries
-Recommended by 98% of users

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

The Windows functions GetTickCount and timeGetTime retrieve the number of milliseconds since the system was started. However, the value is stored in a DWORD, which means that it wraps around to zero every 49.7 days. This article shows how to solve t…
I was prompted to write this article after the recent World-Wide Ransomware outbreak. For years now, System Administrators around the world have used the excuse of "Waiting a Bit" before applying Security Patch Updates. This type of reasoning to me …
With the advent of Windows 10, Microsoft is pushing a Get Windows 10 icon into the notification area (system tray) of qualifying computers. There are many reasons for wanting to remove this icon. This two-part Experts Exchange video Micro Tutorial s…
This is used to tweak the memory usage for your computer, it is used for servers more so than workstations but just be careful editing registry settings as it may cause irreversible results. I hold no responsibility for anything you do to the regist…

627 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question