PC Review
Forums
Newsgroups
Windows 2000
Microsoft Windows 2000 Terminal Server Applications
User Profile not loaded
Forums
Newsgroups
Windows 2000
Microsoft Windows 2000 Terminal Server Applications
User Profile not loaded
![]() |
User Profile not loaded |
|
|
Thread Tools | Rate Thread |
|
|
#1 |
|
Guest
Posts: n/a
|
Hi,
I have an Problem with an Windows 2000 based Terminal Server. The System worked fine so far until the first Domain Controler(and Fileserver) crashed and died. So I was forced to seize the FSMOs on the second Domain Controler, which wasn´t a Problem at all. I had to reinstall the Terminal Server Licencing and so on. Registered the Terminal Server and the Client Licenses as well. No problems so far. Every now and then the Clients receive the following message during the logon process: "Das servergespeicherte Profil ist nicht verfßgbar. Sie werden mit dem lokal gespeicherten Profil angemeldet. Anänderungen an Ihrem Profil werden nicht auf dem Server gespeichert. Wenden Sie sich an den Netzwerkadministrator. Detail: Zugriff verweigert." .... which means roughly: "The server based Profile could not be loaded. You will be connected using the local Profile. Changes on your profile will not be saved. Consult your Administratror. Detail: Access denied." The strange thing is that it work every now and then. I have checked the NTFS Permissions and so on. Looks good to me so far. In the TS Licence Manager I dont see any Licence issued, even if the clients are connected (without receiving the error message). The user connect to the WTS either with FAT-Clients and Thin-Clients. It doesnt seem to make an diffrence. Does anyone has a clue what to look for or what to change? Cheers, Hans |
|
|
|
#2 |
|
Guest
Posts: n/a
|
>
> Hi, 1.Delete the MSLicensing folder form the clients registry Path: HKLM/Software/Microsoft/MSLicensing 2.Check the path to profiles folder if your users have a roaming profile 3. If your using RDP/TCP then check for permissions in RDP properties: Everyone should be a part of that 4. Also could happen that your License database is corrupt More information is required Let me know if you need more help Regards, Sajit Nair > > I have an Problem with an Windows 2000 based Terminal > Server. The System worked fine so far until the first > Domain Controler(and Fileserver) crashed and > died. So I was forced to seize the FSMOs on the second > Domain Controler, which wasn´t a Problem at all. I had to > reinstall the Terminal Server Licencing and so on. > Registered the Terminal Server and the Client Licenses as > well. No problems so far. > Every now and then the Clients receive the following > message during the logon process: > "Das servergespeicherte Profil ist nicht verfßgbar. Sie > werden mit dem lokal gespeicherten Profil angemeldet. > Anänderungen an Ihrem Profil werden nicht auf dem Server > gespeichert. Wenden Sie sich an den Netzwerkadministrator. > Detail: Zugriff verweigert." > ... which means roughly: > "The server based Profile could not be loaded. You will be > connected using the local Profile. Changes on your > profile will not be saved. Consult your Administratror. > Detail: Access denied." > > The strange thing is that it work every now and then. I > have checked the NTFS Permissions and so on. Looks good > to me so far. In the TS Licence Manager I dont see any > Licence issued, even if the clients are connected > (without receiving the error message). The user connect to > the WTS either with FAT-Clients and Thin-Clients. It > doesnt seem to make an diffrence. > > Does anyone has a clue what to look for or what to change? > > Cheers, > Hans |
|
|
|
#3 |
|
Guest
Posts: n/a
|
Hi,
thank you for your help. I am going to erase the mentioned folder in the clients Registry. The path to the serverbased Profiles is 100% accurate. I have checked the permissions on the RDP-TCP Protokoll on my server, which runs in remote administration mode, the only enrollments are System, and Administrators (Win2000). Is there really a need for the Everone-Group? What should I do if the Database is corrupted? Thanks for your help so far. I will get back as soon as possible. Regards, Hans "v_sajit@hotmail.com" wrote: > > > > Hi, > 1.Delete the MSLicensing folder form the clients registry > Path: HKLM/Software/Microsoft/MSLicensing > 2.Check the path to profiles folder if your users have a > roaming profile > 3. If your using RDP/TCP then check for permissions in RDP > properties: Everyone should be a part of that > 4. Also could happen that your License database is corrupt > > More information is required > Let me know if you need more help > > Regards, > > Sajit Nair > > > > > I have an Problem with an Windows 2000 based Terminal > > Server. The System worked fine so far until the first > > Domain Controler(and Fileserver) crashed and > > died. So I was forced to seize the FSMOs on the second > > Domain Controler, which wasnĂ´t a Problem at all. I > had to > > reinstall the Terminal Server Licencing and so on. > > Registered the Terminal Server and the Client Licenses as > > well. No problems so far. > > Every now and then the Clients receive the following > > message during the logon process: > > "Das servergespeicherte Profil ist nicht verfĂÂźgbar. > Sie > > werden mit dem lokal gespeicherten Profil angemeldet. > > Anänderungen an Ihrem Profil werden nicht auf dem > Server > > gespeichert. Wenden Sie sich an den Netzwerkadministrator. > > Detail: Zugriff verweigert." > > ... which means roughly: > > "The server based Profile could not be loaded. You will be > > connected using the local Profile. Changes on your > > profile will not be saved. Consult your Administratror. > > Detail: Access denied." > > > > The strange thing is that it work every now and then. I > > have checked the NTFS Permissions and so on. Looks good > > to me so far. In the TS Licence Manager I dont see any > > Licence issued, even if the clients are connected > > (without receiving the error message). The user connect to > > the WTS either with FAT-Clients and Thin-Clients. It > > doesnt seem to make an diffrence. > > > > Does anyone has a clue what to look for or what to change? > > > > Cheers, > > Hans > |
|
|
|
#4 |
|
Guest
Posts: n/a
|
Maybe I am reading something wrong here, but if you are only using Remote
Administration mode, then there is no need to have TS licenses or any changes to the RDP permissions. Remote Administration mode is only for administrators to do remote administration..remotely. If you are using roaming profiles for your users, it has nothing to do with Terminal Services. Also, by deleting the Licensing key in the registry..beware that if they connect to any other Terminal Servers, you would be deleting those licenses as well. Please take caution, and export the key before deleting for sake of undoing your deletion. G "Hans Heiser" wrote: > Hi, > > thank you for your help. I am going to erase the mentioned folder in the > clients > Registry. The path to the serverbased Profiles is 100% accurate. > I have checked the permissions on the RDP-TCP Protokoll on my server, which > runs in remote administration mode, the only enrollments are System, and > Administrators (Win2000). Is there really a need for the Everone-Group? > What should I do if the Database is corrupted? > > Thanks for your help so far. I will get back as soon as possible. > > Regards, > Hans > > > "v_sajit@hotmail.com" wrote: > > > > > > > Hi, > > 1.Delete the MSLicensing folder form the clients registry > > Path: HKLM/Software/Microsoft/MSLicensing > > 2.Check the path to profiles folder if your users have a > > roaming profile > > 3. If your using RDP/TCP then check for permissions in RDP > > properties: Everyone should be a part of that > > 4. Also could happen that your License database is corrupt > > > > More information is required > > Let me know if you need more help > > > > Regards, > > > > Sajit Nair > > > > > > > > I have an Problem with an Windows 2000 based Terminal > > > Server. The System worked fine so far until the first > > > Domain Controler(and Fileserver) crashed and > > > died. So I was forced to seize the FSMOs on the second > > > Domain Controler, which wasnĂ´t a Problem at all. I > > had to > > > reinstall the Terminal Server Licencing and so on. > > > Registered the Terminal Server and the Client Licenses as > > > well. No problems so far. > > > Every now and then the Clients receive the following > > > message during the logon process: > > > "Das servergespeicherte Profil ist nicht verfĂÂźgbar. > > Sie > > > werden mit dem lokal gespeicherten Profil angemeldet. > > > Anänderungen an Ihrem Profil werden nicht auf dem > > Server > > > gespeichert. Wenden Sie sich an den Netzwerkadministrator. > > > Detail: Zugriff verweigert." > > > ... which means roughly: > > > "The server based Profile could not be loaded. You will be > > > connected using the local Profile. Changes on your > > > profile will not be saved. Consult your Administratror. > > > Detail: Access denied." > > > > > > The strange thing is that it work every now and then. I > > > have checked the NTFS Permissions and so on. Looks good > > > to me so far. In the TS Licence Manager I dont see any > > > Licence issued, even if the clients are connected > > > (without receiving the error message). The user connect to > > > the WTS either with FAT-Clients and Thin-Clients. It > > > doesnt seem to make an diffrence. > > > > > > Does anyone has a clue what to look for or what to change? > > > > > > Cheers, > > > Hans > > |
|
![]() |
|
| Thread Tools | |
| Rate This Thread | |
|
|

Main Page 

