Daxziz
Greetings again everybody.

Last project in school - exam actually wink.gif and what do I drag - WiNS blink.gif and other old cr... school stuff.
I'm a weee bit lost here - I'm been reading up at WiNS and configured a small network with computer from 98 to Windows 2000. Thereby made the foundation to show WiNS and other stuff in its fullest function. This works better than I actually expected it would - especially after I ironed out my bugs which caused the nslookup at the servers to report non-existing doamins and that kinda stuff.

HOWEVER... I also got a second primary option: User Security - and that's of course always a great subject to bring up. Currently I'm a little out of clues to what this actually does involve, but our group has decided to use mandatory roaming profiles and the possibility to only save stuff at their distributed ( mapped ) drive ( maybe DFS ).
And here comes the problem - how on earth do you create those mandatory profiles for Win98 / ME clients at a Win2K DC ? Also keeping in mind that there's a Win2K WS in the play.
I've tested a few things... currently only normal roaming profiles, but sometimes it worked but mostly it didn't... and it always saved the settings at the local computers drive / user folder.

If somebody can provide me with a good detailed guide to work out this magic, would I be very pleased.

Also for those of you which can't help out here, but took the time to read this post thru' - please come with your input of what we should consider when thinking at User Security.

oh and last thing - can you disable the sh.. with just hitting escape and thereby bypassing the login at Win98 / ME.

... how I hate these old crap systems mad.gif


-Daxziz
SKyLiNe
You probably removed the profile path in active directory,
A filled in path means a roaming profile, with a blank profile field,
the user automaticly gets a local profile, hence the saving of the profile to the local machine. For a mandatory profile first create a normal roaming profile,
and once that is working and setup, rename NTUser.dat to NTUser.man.
Now the profile should be mandatory and thus unchangable by normal users.
This is just one example scenario and the creation of certain folders, and the renaming to .man are dependant on the client and server OS's you are going to use in your enviroment. But google can help you with those issues

SKyLiNe
Daxziz
Thx smile.gif


-Daxziz
This is a "lo-fi" version of our main content. To view the full version with more information, formatting and images, please click here.

 
Invision Power Board © 2001-2005 Invision Power Services, Inc.