Every single install I do now requires it to be pushed two time to connect to the SEPM server.
This is still an unfinished issue. The first time I install ANY package, with ANY setting, at any site to my clients. The install works and the package is installed, but the connection to the server NEVER occurs, until I run the setup a second time. When I first install it, the install goes properly, I can see the gold shield, with no error messages, but when I look for it to connect to the server, it NEVER does. This is happening in 100% of my cases now and it is extremely frustrating. I reeally am in desperate need of an answer to this. I am deploying the latest release from Fileconnect, and my servers are Windows 2003 Servers and XP Clients. It never works. :-( Please help with this issue. This is the biggest problem I have with this. I would be greatful for a working solution to this. It is quite agonizing.
Thank you.
Comments
I am upgrading to SEP from 10.1.4 clients to 10.1.8 clients
If that helps at all, I am deploying over existing installations of SAV, the structure has been moved over, and I am creating the packages one by one. I have also tried using the Sylink.xml replacement methods also to no avail. When I deploy to the clients and servers, I am using the deploy selection. I do not use the Migrate from SAV. I have also allowed enough time to synch the clients to the server. The heartbeat is set to 3 minutes, and I gave the copy and install about 45 minutes.
do you mean version 11? <eom>
do you mean version 11? <eom>
Did you try to install the
Did you try to install the package on of client that does not have SAV on it. I mean install the SEP on machine that does not have any antivirus on it. or that has SAV uninstalled?
Yes...
I did do that and it does work, the problem is all of the pc's in my domain HAVE SAV on them already. There is something between the transition that is causing this issue.
Tamper Protection
After the 1st attempt, are you going to a client pc and checking what of SAV is still installed. What do the application logs say.
I am not sure may be you have
I am not sure may be you have a Password Protection policy for SAV that you require the password during the uninstallaition of SAV.
You can use the competitive uninstaller utiliry found in CD2 & uninstall the SAV from all the clients from the Domain & then try to push the SEP over it. This could be a workaround for you.
password for uninstall
My environment had uninstall passwords for SCS (SAV + SCFW). The pushes to those didn't have any issue.
Nope...
There is no password uninstaller, I have not used a password since the days of SAV v 7....If I am having this issue, I am sure there are others with a similar issue, Symantec needs a proper fix for this.
What version Of SAV you were
What version Of SAV you were using?
A variety
10.1.4 clients to 10.1.8 clients
Most are 10.1.7
There is improvement...
...If I use a package with an "Unattended install" my preference is not to use the unattended install, because I do not want users to notice it or interupt it. I want the silent install so it seems to be a seemless transition to the end user.
When deploying the package
if you use default client settings I have found that machines keep information they had previously. I create my packages using the unattended (the key here is the Sylink file that goes with this package is then forced)
The Default
I never use the default, I always create my own package for each site, and then a different feature set. I apply those to the export of the package. I never use the default settings. What you are saying makes sense, but the ONLY difference here is the Unattended setup will force the Sylink to work accordingly, but the silent install requires 2 installations. I really do not want users to see the install taking place at all.
When creating the
When creating the installation package, have you gone into the Client Install Settings area and selected "Remove all previous logs and policies,...." under the Upgrade Settings: ?
That should reset all pre-existing client communications settings.
Even with this setting...
The same thing occurs. 2 Installations. So far, the ONLY fix I see is to use Unattended.
We used the unattended mode
We used the unattended mode when we were on 10.x.... somehow our engineers would suppress any windows the enduser would see via SMS (I think). I'll see if I can get some information on how (the code) they did this.
Even with Unattended
It is not a guarantee, I have 5 that I used UI for and 2 got it right, 3 I am doing again right now, and the server got it right. :-(
I am having the
I am having the same issue. I do not think updating the Sylink file is a viable solution...I know that my superiors wont be satisfied with me rolling out to 3500+ computers all over the world with the "it might work and if it doesnt do this response." Do we have a solution for this is there a setting that I am missing when building my client packages I do not even see the unattended option when setting up my package.
Would you like to reply?
Login or Register to post your comment.