The Powers (and limitations) of Active Directory and Friends I've really been getting into the whole file server and domain login thing these past few days.
I set out to create a simple file server for our home and office computers (two buildings, same physical property and LAN), and stumbled on something that seems quite a bit more powerful.
The basic setup is 8 Win XP Pro clients on a gigabit switch, with a 9th box running SME Server 7.1 (Linux based SMB/Samba file server with Primary Domain Controller and Roaming Profile support).
On my XP computers I am able to login using domain authentication and access the shares.
I've also setup a netlogon.bat file to automatically map shares to drives at login.
Now the questions:
I've noticed that changes to the desktop wallpaper 'travel' with the user to different machines. So I'm guessing that the server stores a configuration file with user prefs?
Is there a list somewhere of the settings that are local vs. server stored?
Second, the server creates a '/home/[username]' share for all users. Can I map that share to a windows folder on the client machine, instead of to a drive?
Say, the user's folder in documents and settings? With the intent being that all files saved to 'my documents', the user's 'desktop' and all user-specific program data live on the central server?
Third, only domain administrators can delete desktop shortcuts! How can I change user permissions for network users? I can only see the local users under 'user accounts' and in 'administrative tools'. The MS documentation says I should see an icon in 'administrative tools' for this purpose, but it isn't there.
The SME Server developers don't really seem to support the 'windows side' of the server package, and the official MS documents assume (naturally) that your running MS AD on WS 2003 or similar.
Thanks for your assistance,
Nick |