Closed
Bug 1075103
Opened 10 years ago
Closed 10 years ago
mdt 2008 auto login during install fails
Categories
(Infrastructure & Operations :: RelOps: General, task)
Tracking
(Not tracked)
RESOLVED
FIXED
People
(Reporter: markco, Assigned: markco)
References
Details
No description provided.
Assignee | ||
Updated•10 years ago
|
Assignee: relops → mcornmesser
Assignee | ||
Comment 1•10 years ago
|
||
20 to 30 % of 2008 machines were be re-imaged were not completing do to auto logon failure. There where 2 separate conditions. One was the administrator account name was changed to root as per GPO but the password was never changed to match the password. The other condition seemed that no combination of possible administrator account names with any of the possible passwords were working. Following the logon failure for the first condition, after log in with the mentioned credentials the install would complete with any other apparent issues.
With either condition, if the machines Domain account was deleted prior to installation the next install would complete without issue. Results on additional installation varied.
We disabled the root name change in the GPO and add a security template import into the production task sequence. The template import changes the administrator name to root. The template is generated by setting up a local security policy to change the name and exporting the policy to an inf file. In the tasks sequence the inf file is copied locally and then imported using a secedit command. After multiple re-images across two machines either condition has not occurred.
We suspect that the issue was being caused by caching on the a DC with the machines domain account. We haven't investigated further because we have an apparent fix, and
we are moving away from domain management of machines.
Q: Do you have anything to add?
We suspect there was some caching issue with the individual domain accounts
Flags: needinfo?(q)
Assignee | ||
Updated•10 years ago
|
Status: NEW → RESOLVED
Closed: 10 years ago
Flags: needinfo?(q)
Resolution: --- → FIXED
You need to log in
before you can comment on or make changes to this bug.
Description
•