|
| | | Forum Newbie
Group: Forum Members
Last Login: 9/25/2007 6:48:03 PM
Posts: 3, Visits: 5 |
| Hi New Boundary, bear with me here a long description;
I am a Sysadmin for a training facility where we often re-image our machines using Microsoft BDD2007 and WDS. During the process the Prism Client is rolled out onto the workstations and following a re-boot it shows up in the console fine. We have two groups of users, educators and students. To share training material, the educators have R/W to certain network drives where the students only have read access. The students and the educators each have their own user, "student" and "educator".
Now the entire process of naming the workstation, choosing the right image for the right computer, joining the domain and pushing out the right "Base" software has been fully automated using BDD.
Except for one little annoying detail; The process ends at a windows login prompt. To solve that I've tried various Auto-logon registry scripts and when tested they work fine, but the BDD process clears all auto-logon information when finishing up, so my changes are wiped clean and I end up at a blank logon prompt again. I want it to end logged in and ready for use.
The naming conventions for the computers are basically just the room and computer number with an "E" added to educator workstations.
To try and solve this, I set up prism to have two configuration groups, student and educator. When a student is logged in, prism detects username and executes a registry import to have that user forever autologon. It works to a degree. But my real problem is that the process is not auto logging on the first time, it needs a username so this won't solve my problem. EXCEPT if I instead of detecting username, I detect computername, and have it log on according to student or educator computernames and then I set the script to run unattended right?
YES, except... it works SOMETIMES. And THAT'S what's bothering me.
Why does it seem to work randomly on and off? It's works like 40 percent of the time.
It's as if the prism server just quits out of the blue, the configuration groups being populated fine but the commands are not executed, not just the unattended command but also the username detection command is sometimes ignored.
Please tell me I have overcomplicated things that there's a much easier or more reliable way to to do it? All I want is to have the student users logged on to the student pcs and the educators logged on the educator pcs automatically. Everything else is automated from one mouse click in the PXE menu.
Prism Deploy 8 running on Windows 2003 R2 fully updated. The clients are all windows XP fully updated as well. Had the exact same thing on version 7. Manual push of software never fails.
Kind regards,
SJO
|
| |
| | | 
Supreme Being
Group: Moderators
Last Login: Yesterday @ 10:05:18 AM
Posts: 655, Visits: 811 |
| | You've come up with a nice process! The only way we are aware of setting up autologon settings is by manipulating some registry settings (HKLM\Software\Microsoft\Windows NT\CurrentVersion\Winlogon), and it takes a reboot before autologon is active. Once a computer is configured for autologon, it takes more registry manipulation and another reboot to turn off autologon. Is that the method you are using? If you send us more detail about your method, perhaps we can run some tests in our lab.
New Boundary Technologies Support
support@newboundary.com |
| |
|
|