Prior to installing the 7.15 VDA session sharing was enabled, ie, one user launching multiple apps would have all applications running on the same server. After installing the 7.15 VDA on one server the user started noticing sessions across different VDA’s. Now all servers are exhibiting this behavior and resources are running low.
We use SEPM 14 version to manage our clients. Most of the time 99% SEP clients are up to date with virus definitions. But every time we get an email stating few of the client are out of date and those clients are random .Even though those clients are showing connected to SEPM with green icon .We usually use smc -stop and -start for some case it may work else we need to reboot the server .In order to avoid reboot we use the Intelligent Updater files and resolve the problem .Do you have any idea why few of the clients failing to download the virus definitions.Those clients were downloading /updating definitions from SEPM without any problem .Can anyone share your experiences .
We have several site servers with deployment soltion installed in our company. All but one can image many machines at a time. I have seen up to 15 machine being imaged at one time. At one of our sites they can ony do 2 at a time.If they try to do more it fails an earier job. Is there any special conguration that needs to be done on the server to allow more? All are using the same global settings. Thansk in advance for any soltions
I am trying to configure the Quarantine console and Quarantine Server on Windows 2008 R2 standard edition as we have symantec protection engine on our Environemnt. I have installed both Console and Server on a same server. But i am unable to connect to the server. Even i don’t see the Quarantine Console services. I have done the reboot after the installtion even though it’s not showing the services of Console. When i am trying to open the Console i am poping up with the window to connect to the server, if i select this computer and click on finish “Can’t Connect to the Server” “Make sure the Quarantine server is installed on the specified machine”. Please some one help with this issue ASAP. I referred the below configuration document
Here is our scenario: We have many Windows 10 laptops that very rarely see our internal company network nor do they see the internet. We have groups of these laptops that are taken to various locations throughout our region and setup on their own closed network using a router that is not connected to a WAN (no internet connectivity). This is done for the day then taken down at the end of the day. The one consistency that they have is that they all can connect to a single server that is set up on the closed network. When not in the field the servers do come back and get connected to our internal network and so they are able to keep Windows and SEP up-to-date. Though the laptops roam between which of the physical servers they are connected to, the servers will always have the same IP address on the closed network (lets use 10.1.1.2 for example). So tablets/laptops can always connect to 10.1.1.2 while on the closed network. I thought that making the servers GUPs and pointing the clients to look for a GUP at 10.1.1.2 might be a solution to how to keep their definitions up-to-date but upon further reading about GUP best practices I read this:
“If the SEP clients you need to update using a GUP are not able to connect to the HTTP port used by the SEPM for client management, consider another method of updating clients.”
Unfortunately it can be many months that pass before the laptops see our internal network and this is usually a manual process when we put hands on each device and update them. Obviously with the laptops being on a closed network there isn’t much of an attack vector and it would be difficult for anything to spread from them as well but ideally we would be able to keep their SEP definitions up-to-date anyway in case staff deviate from our documented policies and processes and connect them another network or plug mass storage devices into them (we do have Windows Group Policy in place but there are some known ways around and we like to try to cover all of our bases).
Does anyone have any suggestions on how we might best keep the SEP clients up-to-date in this scenario?
After updating to 14.2.2 MP1, all the Remote Desktop Servers we support have gone south
There is a Symantec Service Framework created for every user – And it’s using anywher from 1.5 – 5% utilization
This creates ana almost 100% utilization in small environments
I’ve had to remove SEP 14.2.2 MP1 – will re-install older version later
Seem to only affect Server 2012 and above
Server 20008 R2 seems to be ok
Any idea or workaround to fix this ?
Our servers, without stable connection to Internet, are installed with SEP 14.X standard client, and get virus definition update from our internal SEPM server.
I did not know there is a so-called “dark network client” until recently. When I saw the difference between the 2 versions, I was pretty shocked:
Can anyone explain to me the difference about virius definition?
Standard client is “download latest definition only”, “use definition in the cloud”;
while the dark web client is “full set of definition”.
If our servers cannot connect to Internet, does that mean their SEP (standard client) are not able to detect some virus due to lack of some definitions?!?!?!