This content has been marked as final. Show 5 replies
Did you follow instructions in KB 613493?
I've had this happen before when I forgot that laptops connected to the internet, but disconnected to epo/repositories will drop down to using NAIFTP to get updates - and because they're disconnected from epo they haven't yet downloaded the policy changes to prevent this from happening.
If you intend to rollout after testing anyway, i wouldn't worry about it - you just got a few extra test machines you didn't intend....
What we did in our environment to test Engine 5300 was to do the following:
1. Added the Scan Engine 5300 to the Evaluation Branch only.
2. Created a EPO Agent policy called "Evaluation Scan Engine".
3. In this policy under "Update", I configured the scan engine to be pulled from the "Evaluation Branch".
4. Then on select systems/groups I would change these groups/systems to use that newly created policy.
5. This means that "ONLY" these system would receive the new engine.
We did this scenario with the last Engine 5200 and it worked great. Once you are satisfied that the new engine is okay, then you would move it to the "Current Branch".
Mind that at 27th Aug you will need to have all your tests done, for the 5300 will replace the 5200 in the source...
We have already finished our testing and already deployed to ALL systems about 1 1/2 weeks ago.
epo909 : no worries on that because my clients are configured to use my ePO server as the primary respository, NAI as the 3rd choice.
by the way, i've just tried using the method as suggested by twenden and it worked exactly the way i had intended for it to be!
thanks for all the help rendered!