Endpoint Protection

 View Only
  • 1.  SEP deployment

    Posted Dec 14, 2011 08:30 AM

    Hello,

    I am wondering am I able to deploy 32 and 64-bit SEP 12.1 clients under same container? Does it follow best practises, and will it cause technical issues? The problem is that I have 32-bit and 64-bit systems in the same OU, and I don't want to separate them because of that.



  • 2.  RE: SEP deployment
    Best Answer

    Broadcom Employee
    Posted Dec 14, 2011 08:39 AM

    Hi,

    It won't make any problem. You can deploy under same container.

    If you are upgrading existing clients thorugh auto upgrade then SEPM will take care itself.



  • 3.  RE: SEP deployment

    Trusted Advisor
    Posted Dec 14, 2011 09:02 AM

    Hello,

    First, what do you mean by same container??

    Do you mean, you are creating a same folder in which 32 bit and 64 bit packages would be kept for deployment purposes??

    These packages are quite intelligent and they would get installed only when they are find the right type of Operating System (32 bit /64 bit)

    Again, I would recommend you to check this Articles when using installing SEP via GPO.

     

    See Installing clients with Active Directory Group Policy Object.

    See Uninstalling client software with Active Directory Group Policy Object.

     

    Hope that helps!!

     



  • 4.  RE: SEP deployment

    Posted Dec 14, 2011 09:02 AM

    This is new in 12.1 and it should autodetect and use the package necessary.  You should be just fine with one OU :)



  • 5.  RE: SEP deployment

    Posted Dec 15, 2011 01:32 AM

    Container that contains client computers, which in our case is Active Directory OU.

    The question was could I add 32 and 64 bit packages to Install Packages "tab" in SEPM clients view.



  • 6.  RE: SEP deployment

    Broadcom Employee
    Posted Dec 15, 2011 01:50 AM

    client will know which package to take, so having 32 bit & 64 bit for autoupgrade will not have any problems.