Recently I have started working on a project where I have
inherited an existing windows 7 image. I started the project with updating the
existing build and capture task sequence and added IE 9 along with some other
time consuming software to reduce the OS deploy time.
The task sequence ran without any issues, Build and
capture was successful. I have updated Deploy task sequence with newly created
image and deployed to a machine.
When I logged on to the machine first time I have
received below error instead of the desktop.
“The user Profile
Service service failed the logon.
User profile
cannot be loaded.”
I am pretty sure that the previous image never had this
issue.
The issue seems to be appeared only with the newly
captured image and any other accounts other than built-in local administrator
account.
I logged onto newly built machine with built-in
administrator account checked the even viewer logs.
I saw two interesting events related to User Profile Service
(1500) and User Profile General (1509).
The User Profile Service (1500) reports: Windows cannot
log you on because your profile cannot be loaded. Check that you are connected
to the network, and that your network is functioning correctly.
Details – Only part of a ReadProcessMemory or
WriteProcessMemory request was completed.
The User Profile General (1509) event reports: Windows
cannot copy file \\?\C:\Users\Default\AppData\Local\Microsoft\Windows\Temporrary
Internet Files\SQM\iesqmdata_setup0.sqm to location \\?\C:\Venus\Default\AppData\Local\Microsoft\Windows\Temporrary
Internet Files\SQM\iesqmdata_setup0.sqm. This error may be caused by network problems
or insufficient security rights.
Details – Access
is denied.
Based on details of the event viewer, iesqmdata_setup0.sqm is the culprit. I
am not sure how iesqmdata_setup0.sqm file created in the first place, but I believe
it was created when the package was build using IE customisation wizard.
During the deploy task sequence, I have added a step to
delete this file.
Deleting iesqmdata_setup0.sqm
solved the problem.
No comments:
Post a Comment