What you want to do can be done through policies where a number of custom Windows shell items can be specified:
Using Poledit - go to:
User / Windows NT Shell / Custom Shared Folders
~ and/or ~
Computer / Windows NT Shell / Custom Shared Folders
where you can specify custom Start Menu items, custom Desktop items, and custom Program Group items. To make it different by location, use the %logonserver% variable to point to a share on the server that they are logging onto (as long as the share name is consistant on every server) such as -
\\%logonserver%\start
\\%logonserver%\programs
\\%logonserver%\desktop
\\%logonserver%\startup
On each logon server, create the shares and populate with the location-specific items.
This is something that you will need to test in a lab and perfect prior to implimenting it into a production environment.
There are other ways, such as pointing to different folders depending on the IP address assigned to the workstation or laptop (if you are using DHCP), but defining it through the policies is the best way to do it. The policy can even be created for a Global Group that is populated with the roaming users - thus not affecting users who stay in one location.
------------------
BREAKFAST.SYS halted... Cereal port not responding
[This message has been edited by mfutty (edited 08-28-2001).]
Experience: Something you don't get until 10 minutes after you needed it.
Reply With Quote
Bookmarks