behaviour depends on profile-type, how to resolve this?

[tingelton]

Hi,

I have an application that runs fine when logged on as a local admin,
when I log on as a domain-admin the application doesn't run anymore.
After research I found out that a reg key is responsible for this.
[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows
NT\CurrentVersion\ProfileList\<Profile-ID>] "State"=dword:00000100

100 is the same value as for the LOCAL administrator. Problem is that
this key disappears when logging off, logging on again recreates the
key but with the wrong value. I haven't got a clue what this key
really does but it works, although I'm afraid it gives a profile too
much permissions... Anyway finding a solution for a problem without
knowing what it really does, I did some more investigation. After some
more research it seems like this key is responsible for the
profile-type (local, mandatory, roaming). Normally our users have
mandatory profiles, I changed my test-user to roaming and "voila" the
appalication now works properly and also the value in the key is
different, so there must be a link between these two.

But what I still find very strange is WHY doesn't this application run
properly with mandatory profile and WHY does it run properly with a
roaming profile. The profile I used is exactly the same I only changed
ntuser.man to ntuser.dat.

We use flexprofiles to have a roaming functionality with mandatory
profiles but in this case some of our applications still don't work,
can anybody explain this, am I missing something here?

Thanks

 

[Dave Patrick]

Ask the application developer.

--

Regards,

Dave Patrick ....Please no email replies - reply in newsgroup.
Microsoft Certified Professional
Microsoft MVP [Windows]
http://www.microsoft.com/protect

:
| Hi,
|
| I have an application that runs fine when logged on as a local admin,
| when I log on as a domain-admin the application doesn't run anymore.
| After research I found out that a reg key is responsible for this.
| [HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows
| NT\CurrentVersion\ProfileList\<Profile-ID>] "State"=dword:00000100
|
| 100 is the same value as for the LOCAL administrator. Problem is that
| this key disappears when logging off, logging on again recreates the
| key but with the wrong value. I haven't got a clue what this key
| really does but it works, although I'm afraid it gives a profile too
| much permissions... Anyway finding a solution for a problem without
| knowing what it really does, I did some more investigation. After some
| more research it seems like this key is responsible for the
| profile-type (local, mandatory, roaming). Normally our users have
| mandatory profiles, I changed my test-user to roaming and "voila" the
| appalication now works properly and also the value in the key is
| different, so there must be a link between these two.
|
| But what I still find very strange is WHY doesn't this application run
| properly with mandatory profile and WHY does it run properly with a
| roaming profile. The profile I used is exactly the same I only changed
| ntuser.man to ntuser.dat.
|
| We use flexprofiles to have a roaming functionality with mandatory
| profiles but in this case some of our applications still don't work,
| can anybody explain this, am I missing something here?
|
| Thanks
|