Yep, that's what we do here. Everyone's profile is stored on
the server
then their mydocs and desktop folders are redirected to a
share on a
Unix machine running Samba. We put DFS in front of that to
allow us
some flexibility to move things around when needed. The best
part is
that the download times for the profile are minimal since
the two big
data folders are redirected.
Regarding login scripts, I'll second what Graham had to say
on the
subject. Group policy allows you to assign scripts on
Startup, shutdown,
logon and logoff. We also set permissions on the GPO by
group to control
who gets which script. I've pasted a template script we use
to take care
of drive mappings and network printer configs. It's a VBS
script
On error resume next
Dim WSHShell, WSHNetwork, objDomain, DomainString,
UserString, UserObj,
Path, Message, Title
Set WSHShell = CreateObject("WScript.Shell")
Set WshNetwork = CreateObject("WScript.Network")
'Remove old netowrk drives
WSHNetwork.RemoveNetworkDrive "g:",true, true
WshNetwork.RemoveNetworkDrive "h:",true, true
WshNetwork.RemoveNetworkDrive "p:",true, true
WshNetwork.RemoveNetworkDrive "w:",true, true
WshNetwork.RemoveNetworkDrive "s:",true, true
'remove old printers
'Set WSHPrinters = WSHNetwork.EnumPrinterConnections
'For LOOP_COUNTER = 0 To WSHPrinters.Count - 1 Step 2
'If Left(WSHPrinters.Item(LOOP_COUNTER +1),2) =
"\" Then
' WSHNetwork.RemovePrinterConnection
WSHPrinters.Item(LOOP_COUNTER
+1),True,True
' End If
'Next
'add new drives
WSHNetwork.MapNetworkDrive "p:",
"\DFSNAMEsharesprojects",True
WSHNetwork.MapNetworkDrive "g:",
"\DFSNAMEsharesgroups",True
WSHNetwork.MapNetworkDrive "h:",
"\DFSNAMEhomedirhomes",True
WSHNetwork.MapNetworkDrive "k:",
"\DFSNAMEsharescourses",True
WSHNetwork.MapNetworkDrive "w:",
"\DFSNAMEshareswww",True
WSHNetwork.MapNetworkDrive "s:",
"\DFSNAMEsharessoftdist",True
'Add printers
WshNetwork.AddWindowsPrinterConnection
"\printserverroom210"
WshNetwork.AddWindowsPrinterConnection
"\printserverroom5"
WshNetwork.SetDefaultPrinter
"\printserverroom210"
Jack Burris wrote:
> While on the subject of Roaming Profiles and login
scripts, and hoping
> to avoid re-inventing the wheel, has anyone else set up
a computer lab
> environment where users can drop-in, login to the
workstations and
> that would connect them to their profiles and data
stored on the server?
>
> We're using Windows 2003 Server and I've already joined
the Server to
> Campus A.D., and I know it's a matter of Group Policy
for the Folder
> Redirection et al, but I guess I HAVE to use a login
script to set up
> the shares/networked-drives? I guess I originally
thought it could
> all be set via Group Policy.
>
> Also, anyone have a relevant login script they would
want to share?
>
> Thanks,
> Jack Burris
> SSCL
> 3-3770
>
> Gary Lum wrote:
>> Do the roaming profiles need to go thru a mapped
drive (i.e. h:)?
>> Our roaming profiles are pointed to
"\servernamesharename%username
>> " instead of using a mapped drive. Redirected
folders are moved in
>> the same fashion. We also use DFS to add in some
redundancy and
>> flexibility.It's worked rather well and haven't had
any issues
>> related to downloaded roaming profiles
>>
>> Gary
>>
>>
>>
>>
>> Dave Patterson wrote:
>>> Hello,
>>>
>>> Our XP clients currently login both to Novell
Netware 6.5 & Windows
>>> 2003 domains. The clients have several
important parts of their
>>> file system redirected to drives mapped to
novell shares (my
>>> documents, profiles etc). I would like to
migrate off of Novell in
>>> phases, so I am experimenting with mapping the
redirected files to
>>> Windows 2003 file servers shares, but I am
running into a timing
>>> problem. My AD logon script is mapping a drive
to the new windows
>>> file server where several roaming profile items
are stored, but 70%
>>> or so of the time the XP shell loads first and
complains that the
>>> drive path is missing. When I look into the
Windows Explorer, the
>>> drive map is there and available. Files added
to the desktop show
>>> up in the redriected folder on the mapped drive
and vice verse, but
>>> the files already there don't show on the
desktop and error messages
>>> appear. 30% or so of the time, the drive
letter manages to map
>>> before the OS goes looking for it.
>>>
>>> I'd like to compel the XP clients to wait for
the drive mapping to
>>> finish before looking for the redirected
desktop files etc. Any
>>> tips? Thank you in advance.
>>>
>>
>>
------------------------------------------------------------
------------
>> The following was automatically added to this
message by the list
>> server:
>>
>> For information about Micronet, including
subscribing to
>> or unsubscribing from its mailing list and finding
out
>> about upcoming meetings, please visit the Micronet
Web site:
>> <http://micronet.be
rkeley.edu/>.
>
>
>
------------------------------------------------------------
------------
> The following was automatically added to this message
by the list server:
>
> For information about Micronet, including subscribing
to
> or unsubscribing from its mailing list and finding out
> about upcoming meetings, please visit the Micronet Web
site:
> <http://micronet.be
rkeley.edu/>.
------------------------------------------------------------
------------
The following was automatically added to this message by the
list server:
For information about Micronet, including subscribing to
or unsubscribing from its mailing list and finding out
about upcoming meetings, please visit the Micronet Web site:
<http://micronet.be
rkeley.edu/>.
|