symantec corporate enterprise edition

ColdFusion · Post by **ColdFusion** » Sat Dec 11, 2004 1:24 am

So i installed the server side on my computer. Everything appears to be running fine but im wondering where exactly is the Administrator Console ??

CableDude · Post by **CableDude** » Sat Dec 11, 2004 12:41 pm

*paging YOSC

Post by **YeOldeStonecat** » Sat Dec 11, 2004 12:47 pm

When you're running the install on the head Antivirus Server...in the menu you'll see additional tools to install once you've already deployed your main server. Unless you intend to use them, you can skip the alert features, and Quarantine stuff....but the main MMC tools you'll want.

Then you'll see them in Start==>Programs.

The clients to this server, you can set to be installed through the login script, or you can go to each client and drill through network places to the server, you'll see a VPLogon share...drill into that, clt-inst, Win32, a little setup file that will preconfigure install the workstation client.

Make sure on the server itself, you change the live update schedule from weekly, to daily.

ColdFusion · Post by **ColdFusion** » Sat Dec 11, 2004 3:11 pm

Hey Yosc,

Thanks for your reply. I'm trying to figure out what exactly you mean. When running the install it asked if I would be a client or server, and I choose server. I'm running the server off my computer. So it installed, and is sharing the VPLOGON stuff. I did the install on my sisters comp and everything went through fine. It says its connected to MATTO (my computer) and i can view logs of viruses actually found on there computer. I was just thinking there was a more Administrative program to control certain things on their computer like change certain preferences. Also, is it possible to disable their access to the Client Panel in Start -> Programs -> Symantec Client Security ? Here is a screenshot of the install, and the only thing i have in my Programs menu:

Thanks for your help
matt

Faust · Post by **Faust** » Sat Dec 11, 2004 8:21 pm

did you install the administrative tools? not sure what the varience is between versions, but when the server was set up, the app (SAV CE) as well as Administrative Tools were installed in separate processes. the tools show up as Symantec System Center in the start menu.

also, on the other systems (clients), did you install the client, or deploy it (as the install process)? here, when i install it on a client, all i do is "deploy" it, select the server in setup and that's it... no config on the client other than that. actually, can;t do much with it as far as config, since the central server already knows the parameters/control levels for it's clients. on the client system(s), is live update locked out? the main server should handle that and relay the updates on client logon.

YoSC really is the man in this dept. i have only installed it once (the server) here about a year or so ago, and havent had to touch it since..... and, i had some really good help with the setup.

ColdFusion · Post by **ColdFusion** » Sat Dec 11, 2004 9:16 pm

[quote="Faust"]did you install the administrative tools? not sure what the varience is between versions, but when the server was set up, the app (SAV CE) as well as Administrative Tools were installed in separate processes. the tools show up as Symantec System Center in the start menu.

also, on the other systems (clients), did you install the client, or deploy it (as the install process)? here, when i install it on a client, all i do is "deploy" it, select the server in setup and that's it... no config on the client other than that. actually, can]

Faust,

I believe i 'deployed it'. When i try to access the VPHOME share i get "access is denied" and i have no idea why. So what i did was actually transfer all the files in the folder 'CLT-INST' over to the other comp and installed it from there.

Yes auto-update is locked.

It doesnt even ask for a password to modify the settings such as when to scan, autoprotect, email scanning ... all that ... the client computer has full access to those settings and i dont want them to.

I have no idea where this admin centre is. Im using version 9.2

Faust · Post by **Faust** » Sun Dec 12, 2004 12:42 am

well, i'm running version 8.

when i insert the CD and the autorun menu comes up , one of the choices is "install administrative tools" or something like that in addition to "install server", "install client", and "deploy client".

ColdFusion · Post by **ColdFusion** » Mon Dec 13, 2004 8:07 pm

Yosc ???

Post by **YeOldeStonecat** » Tue Dec 14, 2004 6:10 pm

What's underneath the drop down arrow for "Server Components"

Post by **YeOldeStonecat** » Fri Dec 17, 2004 7:48 am

Did you find it yet?

ColdFusion · Post by **ColdFusion** » Sun Jan 02, 2005 5:09 am

YeOldeStonecat wrote:Did you find it yet?

Sorry for the delayed reply! There is nothing listed under 'server components'.

Post by **YeOldeStonecat** » Mon Jan 03, 2005 12:57 pm

What OS is on this "server"? Is it a full blown server? Or workstation? I've not installed the management tools from 9.0, to a workstation OS, although I've done prior versions to a workstation OS and all the MMC tools have been there. I'm wondering if there's something different in 9 that won't install all the stuff to a workstation OS.

koldchillah · Post by **koldchillah** » Tue Jan 04, 2005 4:26 pm

The CD's autostart menu or default setup.exe should have the following options:

Read This First
Install Symantec Antivirus
Install Administrator Tools <-- where to find System Center Console
Browse CD
Exit

You can install the Symantec System Center Console before or after you actually install the AV portion, it is just a simple mmc snap-in.. Regardless, both should be installed from the autostart menu on the CD or the setup.exe straight from the CD's root.

Once you get the system console up and running, go back to the autostart menu a 3rd time and choose 'Install Symantec Antivirus', but stop when you see the following menu:

Install Symantec Antivirus
Deploy Antivirus Client to NT/2000/XP
Deploy Antivirus Server
Return to Main Menu

choose "Deploy Antivirus Client to NT/2000/XP".

The Client Install Utility will appear and you can click NEXT.

On the next window, if you left the VPHOME folder in the default location you don't have to worry about browsing for it so just leave that alone and click NEXT again.

The next window will list available computers on your network and the second column will list any servers it could find. Select the client once, then select the server once and the 'Add' button should light up and you can click finish after all the client stations on your network are added. It will probably ask you for an admin account to allow the client install and the clients may need rebooting, but otherwise you're done setting up the server & clients, the rest is just configuring the little things to suit your needs.

ColdFusion · Post by **ColdFusion** » Wed Jan 05, 2005 5:07 am

Hey guys thanks for your reply's! Long story but i finally got it working .. well almost. When i try to run the Console, i get this error message:

Snap-in Failed to initialize:
Name:<unknown>
CLSID:{103363F4-69F9-11D2-B34C-00104B22D5Df}

when i press in it seems to bring up the console but says "Snap-in Creation failed".

U guys have any idea why its doing this ?

Thanks
matt

Post by **YeOldeStonecat** » Wed Jan 05, 2005 5:17 am

ColdFusion wrote: U guys have any idea why its doing this ?

Thanks
matt

I've seen that from an upgrade, not a clean install.

In add/remove programs, uninstall the console,(delete any desktop shortcut you might have had for it too) reboot, then pop in the CD and reinstall it. Reboot. Try again.

ColdFusion · Post by **ColdFusion** » Sat Jan 08, 2005 9:23 pm

yeah i still cant get it to work. new error message though ... An error occured while trying to connect to the Topology service. Make sure it is properly installed.

koldchillah · Post by **koldchillah** » Sat Jan 08, 2005 10:57 pm

ColdFusion wrote:yeah i still cant get it to work. new error message though ... An error occured while trying to connect to the Topology service. Make sure it is properly installed.

http://service1.symantec.com/SUPPORT/en ... =savce_9.0

CableDude · Post by **CableDude** » Sun Jan 09, 2005 10:58 am

Do you have the original CD?

DeadEye · Post by **DeadEye** » Thu Jun 19, 2008 10:34 am

Snap-in Failed to initialize:
Name:<unknown>
CLSID:{103363F4-69F9-11D2-B34C-00104B22D5Df}

This error you are receiving from the Symantec System Center Console is caused by a setting in the registry when you installed it.

Ref (Release notes for Symantec AntiVirus Coporate Edition 8.1.1)

Starting the Symantec System Center causes a "Snap-In failed to initialize" error when you've installed with the ntfsdisable8dot3namecreation key set to 1
Symptom: If you have HKEY_LOCAL_MACHINE\system\currentcontrolset\control\filesytem\ntfsdisable8dot3namecreation set to 1, after you've installed the Symantec AntiVirus server and Symantec System Center, the launch of the Symantec System Center will produce an error noting that the snap-In failed to initialize.
Resolution: InstallShield's "get short path name" conversion routines do not work correctly with the ntfsdisable8dot3namecreation key set to 1. The workaround is to quote all path names to ensure they are parsed correctly when passing them to DOS commands. The reason the snap-Ins were not initialized correctly was that their path names were saved incorrectly and in a form that they couldn't be accessed to be initialized.

This problem still exists today in SAVCE 10.1.6. And I should also mention that if you install the Symantec System Center Console on other workstations as well, other than the server, and the ntfsdisable8dot3namecreation is set to 1 that it will break the installation of the console.

There is another possible cause, but this one is much more unlikely to be the case. The article is a little long for this post so I'll link it only. (Microsoft Help and Support "Snap-in failed to initialize")

I hope this helps.