Manditory Profile's Win2k

[Dreameater606]

Are manditory profile's copied to the local machine each time a user logs onto a machine or just the first time?

Recently my school parcially upgraded their network to windows 2000. We're thinking about useing manditory profiles. Will the 2k profile still work on the NT machinenes on the netowrk. If not what can we do so that NT and 2k can co exist using manditory profiles.

[AnnMarie]

Hi Dreameater606 - I deleted your duplicate thread in the Windows NT & 2000 Forum as requested. :)

[Spider]

Mandatory profiles are loaded at every log on. That's the essence of
how they work. When a user is logged on they may make changes
to the profile but when they log off the changes are not saved. So when
they log on next session the original mandatory profile is loaded on to
the computer.

The mandatory profile is ntuser.man in Win2K and I
believe it's named ntuser.man in WinNT. I haven't seen a WinNT
machine in awhile so you'd have to look in the \winnt\profiles\user folder
to verify that. That would be named ntuser.dat before making any
changes to mandatory.
(*.dat when using roaming profiles and *.man when using mandatory profiles).

If you do get any errors on that they will show up, when logging
on, as accessing registry errors.

[Dreameater606]

Thanks Spider,
We decided not to go with manditory profiles for the moment because for some reason when we renamed the ntuser.dat to ntuser.man office wouldn't work properly. Any sugestions for why this is happening

[Spider]

You want to be logged into the client machine as Administrator
and make the ntuser.* change then.

[Dreameater606]

We did that.
We copied the user profile that we wanted to use to a network share. Then pointed a test users profile path to that share. The profile loaded fine but office wouldn't work. It just freezed up when ever we tried to use it. The profile worked fine on the local machine but when we made it manditory and put it on the network share it stopped working.

[Spider]

I must admit I don't understand why you would be having this glitch
with Office.

You have the most recent SP3 pack for Office?

This may also be a ether incompatibility. I use 3Com cards always.
I'll check over some stuff when I get back on the network
and see what is going on with what I suspect might be a permissions
selection.

[Dreameater606]

OK

We've got SP3 for Office, SP3 for win2k and all of the required updates from the windows update site.

[Spider]

Ideally mandatory profiling is setup when the network is first
built. I have never personally activated it on an existing network.

I'll look a bit into this and post if I can come up with some similarities
to your situation.

I assumed you tested the profiling after the upgrades and it was
still producing errors in Office.

[Dreameater606]

Yeah it was

[Spider]

When getting a "Cannot Start..." error from an Office program you can
possibly blame a corrupted Mapi32.DLL.

A navy admin is talking about some probs with a network at M$'s mole
technet pages. Have a look here (http://www.microsoft.com/technet/archive/default.asp?url=/technet/archive/columns/inside/09-15-00.asp).