Tom's Guide | Tom's Hardware | Tom's Games
![]() |
![]() |
![]() |
Hi all,
I have over 70 domain win2k/xp pro laptops and workstations, that dont login to the domain, only authenticate via syncd usernames and passwords.
I dont want to give them roaming profiles, as they will never roam, they just login to the local workstation, plus it screw up all the local mail settings (we dont use exchange).
But i need to give them network drives. At the moment i do this via a VBS script in the startup folder that silently maps a drive if a network is found, but as in the case of laptops will go away if no network found.
But this leaves headaches as far extra mappings and other scripted commands.
I have tried assigning scripts to a workstation policy, but that dont work.
If there is no way to have a network driven login script dropped to a non domain user, is there an easy way to migrate the accounts.
I will create a new thread if the only option is to login to the domain.
Cheers
Durx

You could create a new script for the work stations.
create a folder call script on the server and share it. copy you scripts there. Create a temp.doc file in the folder.
If exist \\servername\script\temp.doc goto run
end
:run
\\servername\script\???.vbs
this way you could save all your scripts on ther server and edit them with ease.

Workstation scripts,, but how then would i point the workstations to the script without going to each workstation and editing the existing script.
I was hoping to also delete this existing local script with a central script.
The existing script was dropped via a netware login script, and we have sinced canned netware leaving us no way to script things.
I have tried to run a vbs script via workstation policies, which did not work.
Cheers
Durx

Without the PC's being on the domain you can not update the scrit auto..
But if you create your new scripts and have them in a folder everyone can access you still have a way out.
Create another script that the users on the domain can run mannually when on the domain to delete the old script and copy the new one to the startup folder.
Send everyone a email with a link to it, or post a memo to have them run it.
__________________________________
Personally I would start migrating PC's over to the domain. Its much more secure and easy to mannage.Add the workstation to the doamin.
Log in as the user to create the profile.
Log in as administartor. Give the user Admin rights to the local PC.
copy the contents of the old profile to the new domain profile.
Log in as the user and see if everything is working.

![]() |
SBS 2003 POP Connector Pr...
|
Simple Question with IIS ...
|

This post is quite old and has been locked from receiving new replies. Please create a new posting instead.
| Ads by Google |