I deployed the Virusscan 4.5.1 SP1 upgrade using Epolicy Orchestrator's Global 'Force Install' policy. Now machines running Windows 9x are getting .VXD errors. I know that is bad news. I am wondering if maybe the SP1 is causing these problems. I have'nt seen this happen before just by upgrading. Any suggestions??
Tek-Tips is the largest IT community on the Internet today!
Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!
-
Congratulations Wanet Telecoms Ltd on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!
Getting .VXD errors after using EPO to deploy 4.5.1 upgrade
- Thread starter nosrevlah
- Start date
How EXACTLY are you doing this "Global Force install"? AFAIK, you can't do this as a force install since you'd have to have a .NAP file for the SP to have it as a separate entry in the repository.
The best way is to use the AutoUpgrade task. You'll need the AUTOUPG.ZIP file that's used for SuperDAT deployment in ePO to help you here.
HTH, AVChap
... my $1 worth of advise, 2cents isn't enough due to inflation
The best way is to use the AutoUpgrade task. You'll need the AUTOUPG.ZIP file that's used for SuperDAT deployment in ePO to help you here.
HTH, AVChap
... my $1 worth of advise, 2cents isn't enough due to inflation
- Status
Similar threads
- Locked
- Question
- Locked
- Question
- Locked
- Question
- Locked
- Question