Video Screencast Help
Search Video Help Close Back
to help
New in the Rewards Catalog: Vouchers for "Symantec Technical Specialist" and "Symantec Certified Specialist" exams.

Client automatically switching from computer to user mode

Updated: 15 Sep 2010 | 7 comments
TroyKinney's picture
0 0 Votes
Login to vote

I've seen a few posts regarding this, but nothing that resolves it. 

I have AD integrated groups in the SEPM console.  Version 11.0.5 RU5 (latest as of this date).  When a search is done for unmanaged clients and the client is pushed with the specific settings for the preferred mode as Computer, and the install group to the one desired.  The client is installed, but it immediately switches to user mode and will not switch back. 

There is a couple OUs with users and computers in them.  The names of some administrators are listed in an OU, but not the OU that the client is being installed to or exists in. 

I have uninstalled and reinstalled several times and the same thing happens.  I have exported a client package with the desired settings, installed it with an administrative account  that is not listed in any OU integrated with SEPM.  I then log into the client with an account that is not listed in any OU integrated with SEPM.  The client is moved to the Default Group even though the client is listed in the AD integrated OU to which it was assigned. 

I've tried a sylink drop/replace and that doesn't work either. 

I don't want any clients to be in user mode.  I want the AD integration so groups match.  If anyone else has dealt with this same problem, I'd appreciate any assistance with this. 

Comments

TroyKinney's picture
09
Feb
2010
0 Votes 0
Login to vote

Additional information: This

Additional information:
This appears to happen on new client installs only.  Upgrades from previous version 11 clients do not switch to user mode, staying where they are. 
 

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

This issue was fixed in MR4,

This issue was fixed in MR4, but you say that you have RU5  and if you are still having the issue , then Please contact support on the local support number and then they can have you to chnage all the clients to computer mode using  a Tool

Title: 'Some Symantec Endpoint Protection (SEP) clients switch automatically from "Computer mode" to "User mode"'
Document ID: 2009120314355948
> Web URL: http://service1.symantec.com/support/ent-security.nsf/docid/2009120314355948?Open&seg=ent

Prachand Kumar MCSE-2003 Symantec Technical Specialist (SCTS)

pete_4u2002's picture
09
Feb
2010
0 Votes 0
Login to vote

the client also needs to be

the client also needs to be on RU5.

Mick2009's picture
10
Feb
2010
1 Vote +1
Login to vote

Depends on User Used to Log In to Computers.....

Hi Troy,

If yiou have any User mode clients in the organization, it opens the door for other clients to switch mode under certain circumstances (even in RU5).  I recommend contacting Stymantec Technical Support, who can supply you with a tool that will change all User Mode clients into Computer Mode.

There is an Idea (enhancement request) that you may wish to add your vote to: Restrict the ability to enable User mode

Thanks and best regards,

Mick

With thanks and best regards,

Mick

TroyKinney's picture
15
Mar
2010
0 Votes 0
Login to vote

Submitted a support case

The clients are being upgraded to 11 RU5.  The clients being upgraded do not exhibit the issue.  All new clients starting with version 11 RU5 migrates from computer to user group.  I never had this problem until 11 RU5.  I have opened a support case with Symantec for further assistance or access to the 'tool' that will change mode. 

I voted for the enhancement request restricting the ability to enable user mode. 

Thank you very much for your response!
Troy
 

TroyKinney's picture
15
Mar
2010
0 Votes 0
Login to vote

Batch file(s) work to some degree

Thank you for the referral.  I was able to run the switchusermodetocompmodetool, but the moveclientstogroupbasedonoprangetool will not work well in my environment.  The groups are not based on IP ranges.  We could have group membership based on role and have any one of 5 different subnets assigned.  We also have remote users connecting via VPN that do not fall into any single group.  I suppose I could run the tool individually on small IP ranges, but it would be very time consuming.  If anyone else has been in this predicament, I welcome your thoughts.