We use this actual command and store the icons in the custom folders directory on the server.

$Command = "cmd /c xcopy " + $DQ + "\\$Server\Programs\CustomFolders\$GroupName\*.*" + $DQ + " " + $DQ + "c:\winnt\profiles\$UserName\*.*" + $DQ + "/s >NUL"

Shell $command

That way all you have to do is copy shortcuts to your servers and if the folder exists the files are copied otherwise nothing changes.

Hope this helps.

If you need more info let me know.

We use a utility called shortcut and run SHORTCUT /s to remove this associations.

I'd be VERY careful with one's syntax - especially when writing directly to WORKSTATION user profiles !

This is just a heads-up for everyone in the future !

Here's the scenario ...

1) New NT user account is created in user manager
2) User logs into workstation for first time
3) NT creates workstation profile called c:\winnt\profiles\@userid
4) Scripts are written that reference c:\winnt\profiles\@userid
5) For some reason - user account gets corrupt - (happens with roaming profiles)
6) User account gets deleted from user manager
7) User account is re-created with same name as previous
8) User logs back into workstation with new account
9) NT finds cached version of old account - but SIDS are different
10) NT creates new workstation profile with @userid.000
11) Script no longer works !

Been there - done that !

I always reference workstation profiles with the following...

%userprofile%\desktop

Guaranteed to work every time !

Shawn.

[This message has been edited by Shawn (edited 19 May 2000).]

The purpose of the original q. was to allow me to provide our non-technical admin staff with a method of creating individual user profiles whilst keeping them well away from NT policy admin. The users access their desktop on a Terminal Server + Metaframe server farm.

I've done this by defining a group for each resource ("MS Office", "Email", "Oracle" for example). At login the script scrubs any entries already in the users %userprofile%\desktop, then enumerates all the groups that the user is a member of. If there is a directory in the configuration share with the same name as the group then:
1. Any .lnk files are copied to the users desktop.
2. If a "logon.kix" is present it is run.

The logon.kix is a per-resource script used to set/create sane values for registry entries, and create directories necessary for the resource.

Drive mappings (group "Map C to client") and international settings (group "Locale UK") are also handled by group membership.

I know I've been a little verbose, but maybe the info will help someone else, or more likely expose a fundamental flaw in the design