Learn how to a build a cloud-first strategyRegister Now

x
  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 766
  • Last Modified:

%Homepath% and %windir% are somewhat mixed

On a 2003 server that has been upgraded from 2000 server (long ago, no problems so far), suddenly several installations that should write into c:\winnt started writing into %homedir%\windows !? %homepath% is c:\documents and settings\username.
The variables are all in the expected state and healthy, that is echo %windir% for example still is c:\winnt

I am really worried why it uses %homepath%\windows - since it is an upgrade, the directory windows has never existed.
Also some applications don't work anymore since they are looking for files in %homepath%\windows instead of c:\winnt.

Any suggestions were to start looking?
0
McKnife
Asked:
McKnife
  • 2
  • 2
1 Solution
 
Michael PfisterCommented:
Have you changed the terminal services mode from "Remote Administration mode" to "Application Server mode"?
If yes, you need to switch to install mode before installing any app. Either install via "Add/Remove programs" or issue a

chgusr /install

on the command line before starting your install and a

chgusr /execute

afterwards.

Hope it helps.

Michael

PS:


"Installation Mode
If you put a user's session in installation mode before you install an application, the application is installed in the %SystemRoot% directory instead of the user's home directory. If a user's session is in installation mode, all changes that are made to an application's INI files are written to this central location. Putting the session in installation mode permits Terminal Server to keep track of the user-specific application registry entries and any INI files that the application may install during installation. This permits Terminal Server to automatically propagate these registry keys and files to each user as they are needed by applications while they are in execute mode. After you install an application, return the user's session to execute mode to avoid writing user-specific data to the initial user-global installation. If a session is in installation mode when you install an application, the following steps occur"

Source: http://support.microsoft.com/kb/186498/en-us
0
 
McKnifeAuthor Commented:
Hi mpfister,
so you read about my other problem? It is the same server indeed, so I suppose you are right.
Problem came up initially with a part of an application that had been installed a long time ago before TS were installed. But, when you install TS, the wizard alerts you that some apps might have to be reinstalled - and I was wondering why everything still worked...
Today I had no time, maybe tomorrow I'll be back.
Thanks
0
 
McKnifeAuthor Commented:
You were perfectly right, thanks.
the application that started the trouble (after TS installation) however is even incompatible with TS Mode. There is no way to get it running in application mode, although I reinstalled it, but the rest is ok. I will contact the support.
0
 
Michael PfisterCommented:
Glad it helped to track down the prob.

Michael
0

Featured Post

Independent Software Vendors: We Want Your Opinion

We value your feedback.

Take our survey and automatically be enter to win anyone of the following:
Yeti Cooler, Amazon eGift Card, and Movie eGift Card!

  • 2
  • 2
Tackle projects and never again get stuck behind a technical roadblock.
Join Now