SEPM Issues with MR5
We have recently upgraded from MR4 to MR5 (11.0.5002.333). The clients, endpoint protection manager, database, and quarantine are all MR5. Our server is AD integrated.
Over the last 2 weeks we have had to push the client to newly imaged workstations. When we first upgraded to MR5 it worked without issues. Within the last week or so, when deploying clients using either the find unmanaged clients, or the deployment wizard, the clients show up in the console in either the defualt group or in user mode. Before creating the install package for the deployment wizard, the folder tree in the console was synced with AD, then exported with the proper folder selected along with computer mode.
Fixing the machines that end up in the default group isnt an issue. But I am not sure what to do with the workstations that show up in user mode. I have tried to uninstall the client and reinstall using the conosle, but they still end up in user mode.
Does anyone else have some suggestions on how to fix this issue, or prevent it from happeneing further?
Comments
If you've installed a
If you've installed a SEP client in User Mode while logged in with a specific account (e.g. "administrator") then all future installs made by that account will be User Mode by default.
See this thread: https://www-secure.symantec.com/connect/forums/push-install-computer-mode-actually-puts-it-user-mode
I've personally experienced this problem. Symantec tech support provided me with a script that converted all of the user mode clients back to computer mode. After running the script I was able to move any clients from the Default Group over to their appropriate groups.
Jon
I have not installed any
I have not installed any client as user mode. The thing is, if I use the deployment wizard to deploy 10 clients; 1 of them may install correctly, 6 will install as user mode, and the remaining 3 will end up in the default group. Its really odd.
In our case, we did have most
In our case, we did have most of the clients still installing correctly to the proper groups, some showing up in the Default Group as computers, and some showing up in the Default Group as users. It made no sense to us either, and we could never get anyone to fess up to installing a machine in user mode. (So either someone didn't realize, or they don't want to fess up, or it was a bug.) Either way, our problem was resolved by running the script provided by tech support.
Are you logged in with the same user account for each install?
Jon
Try by using following
Try by using following tool
Tool to move Clients to groups based on IP address(SEPM)
it will change all the clients to computer mode
I am believing this is a bug because in some other thread also i had seen this problem
Any way once you use this tool
and see ..
Please don't forget to mark your thread solved with whatever answer helped you : ) Thanks & Regards Aravind
I have tried using this tool,
I have tried using this tool, it works to some extent. But the next group of clients I deploy, still result in the same issue. I want to avoid having to run a tool everytime I deploy the client.
Ok you said you have
Ok you said you have synchronised the SEPM with AD right?
So can you please let me know if you have imported the OU for users from AD ?
I actually just deleted the
I actually just deleted the integration in the console. All of the clients ended up the default group. The ones that came up as user mode, I converted to computer mode using the console. After doing so, I readded the AD sync, and all is well. I deployed a few clients using the find unmanaged clients, and the deployment wizard, and they installed and showed up as they should.
That is what I was about to
That is what I was about to suggest you.
If your issue is resolved
If your issue is resolved then mark a Solution to this thread so that it would be helpful for others.
Would you like to reply?
Login or Register to post your comment.