I cannot install the System Center on my Windows 2003 Terminal Server. There is this article that says it should be possible

http://www.symantec.com/business/support/index?page=content&id=TECH101675&locale=en_US

However, the instructions are incomplete. They do not mention how to chage out of Application Mode or how to enter Remote Administration Mode in Windows 2003 Terminal Server. Even the Windows knowledge base articles are less than helpful.

Has anyone successfully installed the Symantec System Center on a 2003 Terminal Server?

(BTW - I was successful in doing this on a 2000 Terminal Server)

Thanks,

Jason

does this helps?

http://www.windowsitpro.com/article/terminal-server-and-services/q-how-can-i-check-the-mode-of-a-server-that-s-running-windows-server-2003-terminal-services-or-windows-2000-server-terminal-services-.aspx

I'd have to double-check my resources, but I seem to recall that while Windows 2000 Terminal Server does need to be put into a specific mode to install software, 2003 does not (it is smart enough to do it for you).  I'll be able to look tomorrow.

What specifically is happening when it fails to install?  Is the version really SAV 10.0, or actually 10.1.9 (the most recent build)?  Was there something else on there before (such as an older version of the System Center, 9.x) that could be interfering?

Bear in mind too that the System Center can be installed to any machine (even a workstation) and used as a remote administration tool.  It does not have to be installed to the SAV server.

sandra

I found the following, which is included in a document about Endpoint Protection:

On Windows 2003 Terminal Server, if Application Mode is in use, be sure to install using the "install" user. This can be accomplished by following the document Starting the Installation from Microsoft.

It appears that the default for Terminal Services for Windows 2003 is 'Administration Mode' aka 'Remote Administration Mode', for which no special preparation is needed to install software: 

If you choose to install Terminal Services in Remote Administration mode, no special program installation or configuration work is necessary.  If you choose to install Terminal Services in Application Server mode, installing programs is a little different. ... You must put a Terminal Services server in Install mode to install or remove programs on the server.

(From: http://support.microsoft.com/kb/252330)

I hope this helps.  (I will also see about updating that document.)

Edited to add:  I have added more information to the document you originally found.

sandra
 

do you get any error message?

Installation fails or product malfunctions after installation when installed through Terminal Services

Thank you for looking in this further. Unfortunately the suggestions haven't made a bit of difference.

I've tried several different methods to install the System Center

1) Set Terminal Server services to 'disabled' and rebooted the server prior to installation = installation fails

2) Changed a local Group Policy to enable Remote Desktop connections = installation fails

3) Attempted to install via a remote desktop connection (vs. my typical PC Anyway connection) = installation fails

4) Install via add/remove programs = installation fails

5) Change the user mode per the MS instructions = installation fails

Each failure is the same. The software begins its installation and stops with the error "Symantec System Center cannot be installed on a Terminal Server". FYI - I'm running Windows 2003 SP2 Standard Server.

I understand that the system center can be installed on a different machine. However, I'd like to be able to administrate the clients from the parent server and not rely upon another machine for that purpose.

Thanks once again for helping. If you come across any other routines for me to try, I'll gladly give them a chance.

Jason

Hi jason, 

try this

 Drop to a command prompt, type in change user /install, then install Symantec. When it's done, type in change user /execute.

Is your Terminal Server in Application Mode or in (Remote) Administration Mode?  You only need to switch to the install user if the server's in Application mode.

Is anything at all appearing in the Windows event log?

sandra

Yes, I tried the command prompt manual switch in addition to the add/remove programs method. Both resulted in the same error message.

I'm not 100% certain but it's appearing as though I need to uninstall Terminal Services, then install the system center, and finally reinstall Term Server. Why would this be? There's got to be a simple switch/toggle/bit-flag/registry-setting/something that can be changed to trick the SSC into installing on a Terminal Server.

Thanks for everyones help!

Jason

Hi Sandra,

I've tried various methods to switch into Administration mode. All seem to be successful at changing the server mode but the SSC still won't install. I'm afraid the only solution is to uninstall Term Server ?

In the event log I see two events:

First, the ISScript was successful

Second, the Installation operation failed (evt ID 11708)

Nothing very helpful.  :(

Jason

did u check the install log?

start

run 

%temp%

you will find SSC_inst.log something similar to that ;or else enable msi loggin and paste the logs here

http://support.microsoft.com/kb/223300

I checked that log file. Everything looks a-ok until around line 200 where I find these lines:

MSI (c) (44:B8) [13:27:25:491]: Doing action: CheckRequirements
Action 13:27:25: CheckRequirements.
Action start 13:27:25: CheckRequirements.
MSI (c) (44:38) [13:27:25:507]: Invoking remote custom action. DLL: C:\DOCUME~1\ADMINI~1.CFA\LOCALS~1\Temp\MSI87.tmp, Entrypoint: f1
1: Invoke Function fails, Error = 0x8000ffff
Action ended 13:27:39: CheckRequirements. Return value 3.
MSI (c) (44:B8) [13:27:39:835]: Doing action: SetupCompleteError
Action 13:27:39: SetupCompleteError.
Action start 13:27:39: SetupCompleteError.
Action 13:27:39: SetupCompleteError. Dialog created
MSI (c) (44:94) [13:27:39:913]: Note: 1: 2731 2: 0
MSI (c) (44:94) [13:27:40:976]: Doing action: ISCleanUpFatalExit
Action 13:27:40: ISCleanUpFatalExit.
Action start 13:27:40: ISCleanUpFatalExit.
MSI (c) (44:88) [13:27:40:976]: Invoking remote custom action. DLL: C:\DOCUME~1\ADMINI~1.CFA\LOCALS~1\Temp\MSI88.tmp, Entrypoint: CleanUp
Action ended 13:27:41: ISCleanUpFatalExit. Return value 1.
Action ended 13:27:41: SetupCompleteError. Return value 2.
Action ended 13:27:41: INSTALL. Return value 3.
1: MsiServerStartup ends
Action ended 13:27:39: CheckRequirements. Return value 3.
MSI (c) (44:B8) [13:27:39:835]: Doing action: SetupCompleteError
Action 13:27:39: SetupCompleteError.
Action start 13:27:39: SetupCompleteError.
Action 13:27:39: SetupCompleteError. Dialog created
MSI (c) (44:94) [13:27:39:913]: Note: 1: 2731 2: 0
MSI (c) (44:94) [13:27:40:976]: Doing action: ISCleanUpFatalExit
Action 13:27:40: ISCleanUpFatalExit.
Action start 13:27:40: ISCleanUpFatalExit.
MSI (c) (44:88) [13:27:40:976]: Invoking remote custom action. DLL: C:\DOCUME~1\ADMINI~1.CFA\LOCALS~1\Temp\MSI88.tmp, Entrypoint: CleanUp
Action ended 13:27:41: ISCleanUpFatalExit. Return value 1.
Action ended 13:27:41: SetupCompleteError. Return value 2.
Action ended 13:27:41: INSTALL. Return value 3.
1: MsiServerStartup ends
Action ended 13:27:41: ISMsiServerStartup. Return value 0.
MSI (c) (44:B8) [13:27:41:101]: Destroying RemoteAPI object.
MSI (c) (44:84) [13:27:41:101]: Custom Action Manager thread ending.

There is more to the log file but it's simply a list of properties. I'd prefer not to copy and paste the whole log file in a public forum since it reveals information I'm not entirely comfortable putting up here. If there is something in particular I should be looking for, let me know and I'll happily look for it.

Thanks,
Jason

look for return value 3

paste 20 lines above and below that line, do u have any other antivirus installed on the box?

try this document

Server or client installation stops responding or fails when using Dynamic Disk and no drive C: is available

http://service1.symantec.com/SUPPORT/ent-security.nsf/a7d8859c077770e7882573410063494b/82fc2c9d4772887288256c2f004acd51?OpenDocument

; 

MSI (c) (44:38) [13:27:25:507]: Invoking remote custom action. DLL: C:\DOCUME~1\ADMINI~1.CFA\LOCALS~1\Temp\MSI87.tmp, Entrypoint: f1
1: Invoke Function fails, Error = 0x8000ffff
Action ended 13:27:39: CheckRequirements. Return value 3.

This looks like the first point of failure... I'm not sure what the "Invoke Function fails, Error = 0x8000ffff" means exactly, and I can't find that particular error in our KB.

If there are a lot of items in the temporary directory (C:\DOCUME~1\ADMINI~1.CFA\LOCALS~1\Temp\), try moving them to a different location, even temporarily, and see if that makes a difference.

sandra