Jump to content


lupoz91

Established Members
  • Posts

    10
  • Joined

  • Last visited

Posts posted by lupoz91

  1. Hi all,

    I've updated to SCCM CB 1710, windows server 2012 R2. I'm trying to use the new features to install Surface drivers and Firmwares, but I have it greyed out.

    When I try to check Software Update Points -> Classifications -> "All Classifications" it displays this pop-up :

    "Before you enable the Upgrades classification, you must install WSUS hotfix 3095113 on all software update points in your hierarchy.
    If you do not install this update, the Windows 10 Servicing feature will not properly function. See http://support.microsoft.com/kb/3095113 for more information.
    Only Windows Server 2012 and later versions running WSUS support the Upgrade classification of updates.
    Additionally, to service Windows 10 Version 1607 and later, you must install and configure KB3159706 using the guidance at https://support.microsoft.com/en-us/kb/3159706."

    Unfortunately I've already installed both the KBs on the Server some month ago installing the 1706 version, but it seems is not seeing them.

    How can I fix this? Can I unistall the KB3095113 and reinstall it safely without breaking anything?

     

    sccm.PNG

  2. Hi,

    I've followed the steps @hybrid suggested, but my goal is to update from Windows 10 1607 to 1703. The update is still failing with the same error 0xC1800118.

    But when I try the SQL query 

    select TotalResults = Count(*)
    from tbFile
    where (IsEncrypted = 1 and DecryptionKey is NULL) or (FileName like '%15063%.esd' and IsEncrypted = 0) 
    
     

    this is what I got:

    Msg 207, Level 16, State 1, Line 3
    Invalid column name 'IsEncrypted'.
    Msg 207, Level 16, State 1, Line 3
    Invalid column name 'DecryptionKey'.
    Msg 207, Level 16, State 1, Line 3
    Invalid column name 'IsEncrypted'.

    What does it mean? It seems that something is missing on the SUSDB, also after installing the KB3159706...

     

    Please help me

  3. Hi all,

    I'm having difficulties deployng Crashplan Proe throughout SCCM 2012.

    To customize the installation the .msi needs a folder structure like

    • Parent folder
    • msi
    • folder "custom", that contains some files customized

    =custom-install_win-install-directory.pn

     

    Then I need to run this command: msiexec /i "CrashPlanPROe-x64_Win.msi" /qn CP_SILENT=true

     

    How can I deploy this as an application?

     

    I'm at the frst move with SCCM 2012 and I'd be greatful if someone can help me

     

    Thank you

  4. Luca,

     

    Skype for Business is part of an Office 365 plan. See these articles I've written on how to deploy Office 365

     

    1. http://renshollanders.nl/2014/02/office-365-automatic-deployment-of-office-365-with-mdt/

    2. http://renshollanders.nl/2015/08/office-365-updated-deployment-guide/

    3. http://renshollanders.nl/2015/10/office-365-get-office-365-wave-2016-now/

     

    Be sure to read them in this order, because some information is superseeded by my latest articles.

     

    Cheers! Rens

     

    Thank you for this explanation!

    Probably I'm missing something...

    I've to run setup.exe /download first, let it downlaod the package in SCCM shared folder, and then in SCCM2012 create a package with the install.cmd you proposed in the article?

  5. Hi all,

     

    we have bought some license Skype for Business Plan 2 on Office 365 and I would like to deploy Skype for Business to our clients throughout SCCM 2012.

    When you login on office365 you can download a click-to-run package that starts the installation/downalod of the product.

    There is a way to deploy this software throuhgout SCCM? I cannot find anywhere an offline installer of skype for business.

     

    Thank you for your support

     

    Regards,

     

    Luca

×
×
  • Create New...

Important Information

We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue.