Closed
Bug 671369
Opened 14 years ago
Closed 14 years ago
determine why logon.reg did not get applied in the last batch of slaves
Categories
(Infrastructure & Operations :: RelOps: General, task)
Infrastructure & Operations
RelOps: General
x86_64
Windows Server 2008
Tracking
(Not tracked)
RESOLVED
FIXED
People
(Reporter: armenzg, Assigned: mlarrain)
References
Details
To help others follow properly the individual actionable items needed so we can finish the work on bug 645024 I will spun off this bug.
In the second batch of clone machines (the last 4) we realised that they could not auto-login and from looking at the registry it seems that logon.reg did not get applied when it should have.
The script pretty just needs to run this:
regedit /s %systemroot%\logon.reg
and that should do the trick.
digipengi is borrowing one of the 4 slaves (w64-ix-slave10), moving it back to the cloning vlan and use the slave to debug this issue.
| Assignee | ||
Comment 1•14 years ago
|
||
looks like running the regedit %systemroot%\logon.reg still isn't adding the DefaultUserName"="cltbld"
If I run it by hand it works so I need to see where the issue is.
| Reporter | ||
Comment 2•14 years ago
|
||
(In reply to comment #1)
> looks like running the regedit %systemroot%\logon.reg still isn't adding the
> DefaultUserName"="cltbld"
>
> If I run it by hand it works so I need to see where the issue is.
What is that extra quote in before the equal sign? a typo on the comment?
Could you paste the actual script and see if an extra pair of eyes can catch something?
| Assignee | ||
Comment 3•14 years ago
|
||
Windows Registry Editor Version 5.00
[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Winlogon]
"DefaultUserName"="cltbld"
"DefaultPassword"="*******"
"AutoAdminLogon"="1"
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Winlogon
"AutoLogonCount"=-
| Reporter | ||
Comment 4•14 years ago
|
||
My bad; I meant the actual scripts that runs the command "regedit %systemroot%\logon.reg"
not the actual contents of logon.reg
| Assignee | ||
Comment 5•14 years ago
|
||
regedit %systemroot%\logon.reg
| Reporter | ||
Comment 6•14 years ago
|
||
It seems that MDT adds its own auto login to do the deployment and then removes it at the end.
digipengi is hacking around it by adding a startup script.
Status: NEW → ASSIGNED
| Assignee | ||
Comment 7•14 years ago
|
||
writing a run-once batch file for getting the registry key loaded properly.
Status: ASSIGNED → NEW
| Assignee | ||
Comment 8•14 years ago
|
||
rewrote the MDT cleanup script to do the logon.reg script so it does it without even needing to have the logon.reg script. Pushing an image now to verify 100%
| Assignee | ||
Comment 9•14 years ago
|
||
It works now. Giving Armen w64-ix-slave10 back to test and verify all problems are gone.
| Assignee | ||
Updated•14 years ago
|
Status: NEW → RESOLVED
Closed: 14 years ago
Resolution: --- → FIXED
| Reporter | ||
Comment 10•14 years ago
|
||
FTR we had some machine hit some auto-login issues. Not sure what changed a bunch of them went down in the last week or two.
Updated•12 years ago
|
Component: Server Operations: RelEng → RelOps
Product: mozilla.org → Infrastructure & Operations
You need to log in
before you can comment on or make changes to this bug.
Description
•