Video Screencast Help
Search Video Help Close Back
to help
Not able to make it to Vision this year? Get a sampling in the Best of Vision on Demand group.

Deploying managed client to currently unmanged users

Updated: 22 May 2010 | 6 comments
SysAdmin@Dana's picture
0 0 Votes
Login to vote
This issue has been solved. See solution.

Hi, All -
We've just installed SEPM and are trying to figure out how deploying works.  
Most of our users already have SEP11 or SAV10 installed as unmanged users.  Most are XP.
When I try to deploy via Find Unmanaged Computers the software installs correctly, but the computesr aren't added to the Clients list.  When I manually added them to list and try to scan or update them, I get "clients have not yet connected to server.  You cannot . . ."
Do they need a restart?
Do I have to uninstall the unmanged client first?
Should I use the Deploy wizard instead?

  What's the trick?

   Thanks in advance!

Comments

Vikram Kumar-SAV to SEP's picture
26
Feb
2010
0 Votes 0
Login to vote

Create Clients Install

Create Clients Install package using the steps below and push it to the clients it will become managed.

How to restore/retain client-server communication using custom installation settings
http://service1.symantec.com/SUPPORT/ent-security.nsf/docid/2008052008163148




Prachand's picture
26
Feb
2010
0 Votes 0
Login to vote

Do they need a

Do they need a restart?
---No

Do I have to uninstall the unmanged client first?
---No

Should I use the Deploy wizard instead?
--yes , but first create new package with new coomuincation settings and then push that particular pacakge.

Title: 'How to create a client install setting to remove previous logs, policies and reset the client-server communication settings.'
Document ID: 2009042408004148
> Web URL: http://service1.symantec.com/support/ent-security....

Title: 'How to restore/retain client-server communication using custom installation settings without having to use the sylink drop tool.'
Document ID: 2008052008163148
> Web URL: http://service1.symantec.com/support/ent-security....

Prachand Kumar MCSE-2003 Symantec Technical Specialist (SCTS)

SysAdmin@Dana's picture
26
Feb
2010
0 Votes 0
Login to vote

Thanks for the replies. Does

Thanks for the replies.
Does this mean the default 32 and 64-bit install packages don't have the proper communication settings?
How does the Deploy & Migrate wizard differ from an install via FInd Unmanged Computers?

Prachand's picture
26
Feb
2010
2 Votes +2
Login to vote

No , that is not case , they

No , that is not case , they have they have correct commuincation setting. But when a Client is installed and if we push a new pacakge , the new pacakge gets installed but the commuincation settings is not changed, it keeps the old setting. So while creating the new pacakge we need to selcet Remove all previous logs and policies, and reset the communication settigs

d.JPG

Prachand Kumar MCSE-2003 Symantec Technical Specialist (SCTS)

Vikram Kumar-SAV to SEP's picture
26
Feb
2010
2 Votes +2
Login to vote

 Its the same thing, however

 Its the same thing, however in Migrate and Deploy wiz you can deploy with a exported packages.
Fine Unmanaged computers use built in packages.

you can deploy the same thing using FInd Unmanaged computers as well. Just add those client install settings and then go to Find Unmanaged computers search for clients then scroll down and select the client install settings.

They have proper settings but once you have a client install as unmanaged it will have its won communication settings. so when you deploy the package it will only upgrade the client but not change its communication settings so a unmanaged remains unmanaged.

SysAdmin@Dana's picture
26
Feb
2010
0 Votes 0
Login to vote

"Remove all previous logs and

"Remove all previous logs and policies, and reset the communication settigs" was the trick!  Thanks!