This content has been marked as final. Show 17 replies
NO as you cant place VSE into a different branch only stuff like dats/patches and engines.
what is the diff between the 2 packages?
Policy enforcement from EPO should be able to cover most situations
Tony - is this "still" true ? - I thought I read somewher that ePO 4 supported checking the other product packages into the differnet Repository Branches and deploying accordingly ? :confused:
P.S. - don't have an ePO 4 test system to try on yet sad
The repositories have to be different.
PCs have ePO and McAfeeHTTP and Servers have only McAfeeHTTP.
I thought the different branches exist to test some new .DAT...but I don't think it's the way to fixe my problem sad
Well im not yet on sp4 only 3 (but i dont see this in readme for 4) and I can only check point products into current, although other crud as I said before will go into the other strand.
set the repositories through the agent policy and assign it to a group containing the servers or to a TAG group for servers based on a query, no need for seperate packages.
Ok Thanks a lot ! Have a good day happy
What am I missing (again:D) Tony ?
How does this allow deployment of two differently configured AV PAckages to servers and clients ?
I - as an ePO user - understand that using the server/workstation polices that they can both have differnet AV Policies and settings applied but this isn't quite the same as what "seems" to have been asked for ?
Tony - doesn't help the OP much but see this topic for enabling the package check in to alternate branches in ePO 4 :-
LINK removed Off topic - MOD
The "restriction" is that for some bizarre reason the deployment task seems to always use what's in the "current" branches... :mad:
So what are the goal of using the other branches if we cannot use ? !
Edit : What's this link Jim ? silly