10.3.181.23 via SCUP

Any idea when Flash 10.3.181.23 will be pushed out to the catalog for SCUP?
Additionally, any idea when we might get the plugin handled through the catalog? Not sure why it would only be handing out the activex version, doesn't seem to make any logical sense.

Hi, well so much for trying that. I did review your thread and noticed that with FP 10.3.181.14 you didn't have this issue.
Also there could have been a glitch when updating to the 10.3.181.23. That would have activated the UAC to give you a warning about trusting Adobe. Do you recall seeing that at that time?
A couple of the others that had to turn the UAC off so Flash Player would work don't recall the UAC prompt.
It sounds like it's "stuck" or something. Seems to be acting as if it's still waiting to be "allowed" to Install Flash Player.
Hopefully an answer will be forthcoming soon.
Thanks,
eidnolb

Similar Messages

  • Adobe Reader 11 Update via SCUP

    Hi all,
    i'm updating Adobe Reaer via SCCM and SCUP and the published catalogs from Adobe.
    When importing the updates i do not see the MUI Update for Version 11.0.5, but the not MUI Version is available.
    is this update published later what do i wrong?
    Thanks a lot

    I'm a bit sorry, I've used the non MUI version for deployment, it was the German 11.0.04 Package.
    11.0.05 Deployment via SCUP was done without any problems.
    I tried "msiexec /update AdbeRdrUpd11006.msp" with Logging Option and this is the output (It's a bit in german I hope its not a problem):
    === Verbose logging started: 24.01.2014  09:53:11  Build type: SHIP UNICODE 5.00.7601.00  Calling process: C:\WINDOWS\system32\msiexec.exe ===
    MSI (c) (CC:14) [09:53:11:008]: Font created.  Charset: Req=0, Ret=0, Font: Req=MS Shell Dlg, Ret=MS Shell Dlg
    MSI (c) (CC:14) [09:53:11:008]: Font created.  Charset: Req=0, Ret=0, Font: Req=MS Shell Dlg, Ret=MS Shell Dlg
    MSI (c) (CC:5C) [09:53:11:018]: Resetting cached policy values
    MSI (c) (CC:5C) [09:53:11:018]: Machine policy value 'Debug' is 0
    MSI (c) (CC:5C) [09:53:11:018]: ******* RunEngine:
               ******* Product: {AC76BA86-7AD7-1031-7B44-AB0000000001}
               ******* Action:
               ******* CommandLine: **********
    MSI (c) (CC:5C) [09:53:11:018]: Machine policy value 'DisableUserInstalls' is 0
    MSI (c) (CC:5C) [09:53:11:047]: Cloaking enabled.
    MSI (c) (CC:5C) [09:53:11:047]: Attempting to enable all disabled privileges before calling Install on Server
    MSI (c) (CC:5C) [09:53:11:050]: End dialog not enabled
    MSI (c) (CC:5C) [09:53:11:051]: Original package ==> C:\WINDOWS\Installer\1ba82.msi
    MSI (c) (CC:5C) [09:53:11:051]: Package we're running from ==> C:\WINDOWS\Installer\1ba82.msi
    MSI (c) (CC:5C) [09:53:11:055]: APPCOMPAT: Uninstall Flags override found.
    MSI (c) (CC:5C) [09:53:11:055]: APPCOMPAT: Uninstall VersionNT override found.
    MSI (c) (CC:5C) [09:53:11:055]: APPCOMPAT: Uninstall ServicePackLevel override found.
    MSI (c) (CC:5C) [09:53:11:055]: APPCOMPAT: looking for appcompat database entry with ProductCode '{AC76BA86-7AD7-1031-7B44-AB0000000001}'.
    MSI (c) (CC:5C) [09:53:11:055]: APPCOMPAT: no matching ProductCode found in database.
    MSI (c) (CC:5C) [09:53:11:060]: MSCOREE not loaded loading copy from system32
    MSI (c) (CC:5C) [09:53:11:062]: Opening existing patch 'C:\WINDOWS\Installer\1e65cb.msp'.
    MSI (c) (CC:5C) [09:53:11:063]: Original patch ==> C:\Users\xxx\Desktop\AdbeRdrUpd11006.msp
    MSI (c) (CC:5C) [09:53:11:063]: Patch we're running from ==> C:\Users\xxx\Desktop\AdbeRdrUpd11006.msp
    MSI (c) (CC:5C) [09:53:11:063]: SOFTWARE RESTRICTION POLICY: Verifying patch --> 'C:\Users\xxx\Desktop\AdbeRdrUpd11006.msp' against software restriction policy
    MSI (c) (CC:5C) [09:53:11:063]: SOFTWARE RESTRICTION POLICY: C:\Users\xxx\Desktop\AdbeRdrUpd11006.msp has a digital signature
    MSI (c) (CC:5C) [09:53:15:798]: SOFTWARE RESTRICTION POLICY: C:\Users\xxx\Desktop\AdbeRdrUpd11006.msp is permitted to run at the 'unrestricted' authorization level.
    MSI (c) (CC:5C) [09:53:15:798]: SequencePatches starts. Product code: {AC76BA86-7AD7-1031-7B44-AB0000000001}, Product version: 11.0.04, Upgrade code: {A6EADE66-0000-0000-484E-7E8A45000000}, Product language 1031
    MSI (c) (CC:5C) [09:53:15:798]: PATCH SEQUENCER: verifying the applicability of minor upgrade patch {AC76BA86-7AD7-0000-2550-7A8C40011005} against product code: {AC76BA86-7AD7-1031-7B44-AB0000000001}, product version: 11.0.04, product language 1031 and upgrade code: {A6EADE66-0000-0000-484E-7E8A45000000}
    MSI (c) (CC:5C) [09:53:15:799]: Note: 1: 2262 2: _Tables 3: -2147287038
    MSI (c) (CC:5C) [09:53:15:799]: Note: 1: 2262 2: _Columns 3: -2147287038
    MSI (c) (CC:5C) [09:53:15:799]: PATCH SEQUENCER: minor upgrade patch {AC76BA86-7AD7-0000-2550-7A8C40011005} is applicable.
    MSI (c) (CC:5C) [09:53:15:799]: PATCH SEQUENCER: verifying the applicability of minor upgrade patch C:\Users\xxx\Desktop\AdbeRdrUpd11006.msp against product code: {AC76BA86-7AD7-1031-7B44-AB0000000001}, product version: 11.0.04, product language 1031 and upgrade code: {A6EADE66-0000-0000-484E-7E8A45000000}
    MSI (c) (CC:5C) [09:53:15:800]: PATCH SEQUENCER: minor upgrade patch C:\Users\xxx\Desktop\AdbeRdrUpd11006.msp is not applicable.
    MSI (c) (CC:5C) [09:53:15:801]: SequencePatches returns success.
    MSI (c) (CC:5C) [09:53:15:801]: Final Patch Application Order:
    MSI (c) (CC:5C) [09:53:15:801]: {AC76BA86-7AD7-0000-2550-7A8C40011005} -
    MSI (c) (CC:5C) [09:53:15:801]: Other Patches:
    MSI (c) (CC:5C) [09:53:15:801]: Unknown\Absent: {AC76BA86-7AD7-0000-2550-7A8C40011006} - C:\Users\xxx\Desktop\AdbeRdrUpd11006.msp
    Das Upgrade kann nicht vom Windows-Installationsdienst installiert werden, da das zu aktualisierende Programm nicht vorhanden ist oder eine andere Version des Programms mit dem Upgrade aktualisiert wird. Überprüfen Sie, ob das zu aktualisierende Programm vorhanden ist und das richtige Upgrade verwendet wird.
    C:\WINDOWS\Installer\1ba82.msi
    MSI (c) (CC:5C) [09:53:15:802]: Produkt: Adobe Reader XI (11.0.04) - Deutsch - Update "{AC76BA86-7AD7-0000-2550-7A8C40011006}" konnte nicht installiert werden. Fehlercode 1642. Weitere Informationen sind in der Protokolldatei C:\temp\msi2.log enthalten.
    MSI (c) (CC:5C) [09:53:15:803]: Ein Update wurde durch Windows Installer installiert. Produktname: Adobe Reader XI (11.0.04) - Deutsch. Produktversion: 11.0.04. Produktsprache: 1031. Hersteller: Adobe Systems Incorporated. Updatename: {AC76BA86-7AD7-0000-2550-7A8C40011006}. Erfolg- bzw. Fehlerstatus der Installation: 1642.
    MSI (c) (CC:5C) [09:53:15:803]: Note: 1: 1708
    MSI (c) (CC:5C) [09:53:15:803]: Produkt: Adobe Reader XI (11.0.04) - Deutsch -- Installation fehlgeschlagen.
    MSI (c) (CC:5C) [09:53:15:804]: Das Produkt wurde durch Windows Installer installiert. Produktname: Adobe Reader XI (11.0.04) - Deutsch. Produktversion: 11.0.04. Produktsprache: 1031. Hersteller: Adobe Systems Incorporated. Erfolg- bzw. Fehlerstatus der Installation: 1642.
    MSI (c) (CC:5C) [09:53:15:806]: MainEngineThread is returning 1642
    === Verbose logging stopped: 24.01.2014  09:53:15 ===
    Do you have any hints what could be the problem?

  • Flash Update via SCUP Problem

    Hello,
    I am deploying Updates via SCUP and SCCM to hundreds of Computers.
    Fortunately Adobe provides an SCCM Update Catalog for both Adobe Flash ActiveX and Adobe Flash Plugin.
    But now my Problem:
    After publishing the Update via SCCM, the client is not supposed to be interfered with the Update Progress (which is working)
    I figured the Updater works like this:
    First SCCM checks if a Update needs to be deployed, if this is the case, The Flash Updater begins.
    First the old Flash Version is beeing uninstalled.
    But now: if the Client has a Browser Window (IE, or Firefox) open, the Updater is not able to install the new Flash Version and quits with an Error.
    This leaves the Client PC without any Flash (because its being uninstalled before)
    How can I prevent Flash being uninstalled due to the Update progress not working while a Browser window is open?
    Thank you very much!
    Sincerely Martin

    You might get better results asking in the Flash Player forum rather than here in the Flash Pro forum.  Here's a link:
    http://forums.adobe.com/community/flashplayer
    If you are hoping for an answer from an Adobe employee, you should be aware that these are primarily user-to-user forums.

  • Updating Flash Player ActiveX / Plugin via SCUP / SCCM

    Hello,
    I am deploying Updates via SCUP and SCCM to hundreds of Computers, mostly with Windows 7 x64.
    Fortunately Adobe provides an SCCM Update Catalog for both Adobe Flash ActiveX and Adobe Flash Plugin.
    But now my Problem:
    After publishing the Update via SCCM, the client is not supposed to be interfered with the Update Progress (which is working)
    I figured the Updater works like this:
    First SCCM checks if a Update needs to be deployed, if this is the case, The Flash Updater begins.
    First the old Flash Version is beeing uninstalled.
    But now: if the Client has a Browser Window (IE, or Firefox) open, the Updater is not able to install the new Flash Version and quits with an Error.
    This leaves the Client PC without any Flash (because its being uninstalled before)
    How can I prevent Flash being uninstalled due to the Update progress not working while a Browser window is open?
    Thank you very much!
    Sincerely Martin

    Exactly the same issue here (see http://forums.adobe.com/message/6285043#6285043). We have stopped the deployment of that package since nearly every second client is affected by this. It seems that the installation package does uninstall the flash player ocx (both 32-bit and 64-bit), but does not install the new version.
    I remember there was a bug at the beginning of this year, where the install package did install the new version, but marked it as "failed" in SCCM software center.. Just a few days later there was a new package in SCUP with the same version number...

  • Adobe Updates via SCUP

    I am attempting to push out updates for Adobe products using SCUP but am running into a strange issue when clients attempt to install them.
    The clients all see that flash player 11.9.900.170 is available and a required update based on the version currently installed, however when they attempt to install the update, UpdatesDeployment.log reports error 0x80240017 indicating the update is not applicable.
    I thought maybe it was due to the version the clients were currently on (11.7.x.x) so I manually updated a couple to another version (11.9.900.117 then 11.9.900.152 when that failed) to see if that would make a difference, but every time it was the same
    result.
    Has anyone experienced this/found a solution?

    I have seen issues with the rules multiple times. Open the Flash Player package in SCUP and verify that the detection rules are correct.
    Kent Agerlund | My blogs: blog.coretech.dk/kea and
    SCUG.dk/ | Twitter:
    @Agerlund | Linkedin: Kent Agerlund |
    Mastering ConfigMgr 2012 The Fundamentals

  • CU4 Client Update via SCUP

    Anyone else seen issues with this update getting stuck on "Installing"?  Followed usual procedure, deployed to around 5,000 client but seeing the number of clients reporting in as CU4 growing very slowly and reports of it being stuck in
    Software Centre...

    I've recently used this to update my lab environment:
    http://www.petervanderwoude.nl/post/publish-cumulative-updates-of-configmgr-via-system-center-updates-publisher/
    I've not encountered any problems with that. Have you verified the client log files for any issues?
    My Blog: http://www.petervanderwoude.nl/
    Follow me on twitter: pvanderwoude

  • SCUP questions

    so I have everything setup, I basically published everything and created 3 ADR's in SCCM and I'm waiting for the sync to sccm, so far the sync keeps timing out, I'm guessing that might be normal at this point??
    Sync failed: The operation has timed out. Source: Microsoft.UpdateServices.Internal.DatabaseAccess.ApiRemotingCompressionProxy.GetWebResponse
    Anyway, does SCUP put update in WSUS which then get picked up by SCCM ADR's; is that how it works?
    How often does SCUP check for vendor updates?
    Do I have to go in and publish SCUP updates every time?
    Since I have ADR's do I have to create rules in SCUP?
    When new updates come in can I easily distinguish them from previously published updates?
    I used automatic, should I have used Full content when I published?
    instead of having 1 publication should I have 3, one for each vendor?
    Should I add new updates to existing publications or create new ones?
    How does windows update know if Adobe / Dell, Hp needs and update?
    Any tips and tricks would be very helpful, thanks!!

    Where exactly are you getting the sync failure message at?
    That's kind of how it works, but it's missing some relevant detail.
    - You publish update via SCUP to the WSUS catalog (these updates are actually never shown in WSUS though).
    - ConfigMgr syncs with the WSUS catalog
    - ADR references ConfigMgr to create update groups
    How often does SCUP check for vendor updates?
    - It only checks when you start SCUP. SCUP is not a service, it's simply an application.
    Do I have to go in and publish SCUP updates every time?
    - Yes.
    Since I have ADR's do I have to create rules in SCUP?
    - SCUP has no rules so have no idea what you are referring to.
    When new updates come in can I easily distinguish them from previously published updates?
    - Assuming you are talking about into ConfigMgr, that depends upon who created the updated and how well they created it. All updates have a unique ID at the end of the day and should be named uniquely also.
    I used automatic, should I have used Full content when I published?
    - Automatic publishing in SCUP is based upon compliance of systems for a particular update. IMO, it holds no value and should not be used.
    instead of having 1 publication should I have 3, one for each vendor?
    - Publications are simply groups of updates for organizational purposes. You can group updates however you like.
    Should I add new updates to existing publications or create new ones?
    - Sam answer.
    How does windows update know if Adobe / Dell, Hp needs and update?
    - I have no idea what this means. Are you asking about how a client knows it requires an update or how SCUP knows that there is a new version of the catalog, or something else?
    Jason | http://blog.configmgrftw.com | @jasonsandys

  • Reader SCUP confusion - flawed detection logic?

    I'm starting to test the deployment of Reader updates via SCUP.
    What I'm seeing is that Config Manager says I have X number of clients that require Reader 11.0.n - fine.
    It seems confused about what systems need which update, though.  E.g. it says that my workstation requires 11.0.2, 11.0.5, and 11.0.8 even though I'm running 11.0.10.
    What am I missing, here?

    ...or maybe it didn't actually downgrade.  Hard to tell.
    Help-->About says it's 11.0.08.  Programs and Features says it's 11.0.08.  SCCM report says it's 11.0.08.
    Properties of AcroRd32.exe say it's 11.0.10.32.
    So the actual executable is the right version, but parts of the product itself are confused at to what version it is.  Maybe some of the other 192 files are the wrong version, but Adobe only knows.

  • Reader SCUP problem - detection logic issue?

    Sorry about crossposting, but frankly the Adobe forum navigation is atrocious, so when I originally posted this to the general Reader forum, I was unaware that this forum even existed.
    Anyway...
    I'm starting to test the deployment of Reader updates via SCUP.
    What I'm seeing is that Config Manager says I have X number of clients that require Reader 11.0.n - fine.
    It seems confused about what systems need which update, though.  E.g. it says that my workstation requires 11.0.2, 11.0.5, and 11.0.8 even though I'm actually running 11.0.10.
    SCUP 2011, SCCM 2012 SP1
    Anyone know what's going on/what I need to look for, here?

    ...or maybe it didn't actually downgrade.  Hard to tell.
    Help-->About says it's 11.0.08.  Programs and Features says it's 11.0.08.  SCCM report says it's 11.0.08.
    Properties of AcroRd32.exe say it's 11.0.10.32.
    So the actual executable is the right version, but parts of the product itself are confused at to what version it is.  Maybe some of the other 192 files are the wrong version, but Adobe only knows.

  • SCUP - WSUS - SCCM CreateDirectory failed

    Im trying to publish updates via SCUP, but i get the error message below. It did work once during testing but it will no longer publish. Im am using SCCM 2012R2 WSUS 4.5, i created a cert in SCUP (after doing the registry fix) and exported that to the trusted
    root and trusted publishers. The Cert public key is 2048 bits .
    Error Scup2011.9
    Publisher.PublishPackage PublishPackage(): Operation Failed with Error: CreateDirectory failed
       at Microsoft.UpdateServices.Internal.BaseApi.Publisher.PublishPackage(String sourcePath, String additionalSourcePath, String packageDirectoryName, Boolean dualSign, String httpTimeStamp)
    PublishItem: Exception occurred during publishing: CreateDirectory failed$$<Updates Publisher>

    Hi,
    Please make sure C:\WSUS\UpdateServicesPackages share directory and set these permissions:
    Administrators Group – Full Control
    Network Service – Full Control
    System – Full Control
    Users Group – Read, List Folder, Read & Execute
    For more information:
    Proper permissions for the SCUP UpdateServicesPackages folder
    http://myitforum.com/myitforumwp/2012/12/21/proper-permissions-for-the-scup-updateservicespackages-folder/
    Note: Microsoft provides third-party contact information to help you find technical support.
    This contact information may change without notice. Microsoft does not guarantee the accuracy of this third-party contact information.
    Best Regards,
    Joyce
    We
    are trying to better understand customer views on social support experience, so your participation in this
    interview project would be greatly appreciated if you have time.
    Thanks for helping make community forums a great place.

  • Hi i have planned to deploy firefox latest version vis SCUp (syste center update publisher )

    hi i have planned to deploy firefox latest version vis SCUp (system centre update publisher kindly let me know the silent key to install via scup by disabling automatic updates
    jeevan

    Shouldn't you do the following things (see also:
    http://technet.microsoft.com/en-us/library/hh134743.aspx):
    Add Windows Language is French to the top AND;
    Change the second AND to an OR;
    Add the WMI Query to the new OR (so it's at the same level as the
    Windows Version = Windows 7 SP1);
    Remove the last OR (as it's not being used anymore).
    My Blog: http://www.petervanderwoude.nl/
    Follow me on twitter: pvanderwoude

  • SCUP Publishing - CM 2012 R2: What RBAC rights are required?

    Hi,
    I have integrated SCUP 2011 with CM 2012 R2.  CM 2012 R2 is being used in a very large environment.  I would like to allow a small team within my organization the ability to publish updates using SCUP to CM 2012 R2.  Currently, I am doing
    this job using an account that has full rights to CM 2012R2.
    What is the minimum level rights needed to publish SCUP 2011 updates to CM 2012?

    The real thing of publishing updates via SCUP is not part of RBAC, because SCUP only publishes the information to WSUS. If you mean the permissions required to work with the update data in ConfigMgr then the out-of-the-box answer would be the
    Software Update Manager role. Simply because after the updates are synced into ConfigMgr, they need to be treated as normal updates.
    My Blog: http://www.petervanderwoude.nl/
    Follow me on twitter: pvanderwoude

  • SCUP 2011 - Dell Driver Updates

    Hi,
    Im facing a issue with deploying Dell Driver update (for Wireless adapter). I have
    SCUP 2011 server integrated with ConfigMgr 2007, releasing updates for Adobe products without any problem. 
    This week for a first time we decided to update drivers via SCUP as well but when we Publish an Update and Deploy it to a test environment via SCCM workstations reporting that Update is Not Required. 
    I know that this is very specific problem to Dell Driver update but I believe that Im not the only one who manages bigger amount of Dell workstations. 
    I would like to ask if somebody came across similar issue and have some advice for me?
    Few details:
    This is a update im trying to deploy:
    http://www.dell.com/support/drivers/us/en/04/DriverDetails/DriverFileFormats?c=us&s=bsd&cs=04&l=en&DriverId=WF26J
    Test boxes are with driver version 5.100.235.12
    UpdatesDeployment.log shows only following line regarding this update: 
    Added update (Site_374FD2B1-3E03-4A84-AE2D-49D0FC93F63C/SUM_928ae428-46d2-4ccf-b4ee-cf5ea9cf53fa) to the targeted listAssignment {A8B92E94-EDA5-4885-9999-9850F47C9BFB} has total CI = 1
    Assignment ({A8B92E94-EDA5-4885-9999-9850F47C9BFB}) received activation trigger
    Detection job ({7B469A4D-1492-45B9-911E-D426BBE41A17}) started for assignment ({A8B92E94-EDA5-4885-9999-9850F47C9BFB})
    DetectJob completion received for assignment ({A8B92E94-EDA5-4885-9999-9850F47C9BFB})
    I didnt find any trace of Update ID (928ae428-46d2-4ccf-b4ee-cf5ea9cf53fa ) in any other logs which I find strange because Im missing part where update was identified as NOT REQUIRED.
    Installable Rules for update from Dell Catalog are let say general, it checks if client PC is Dell and if it has correct OS version/architecture.
    thanks in advance.
    JK

    Yes, I know this is an old post, I’m trying to clean them up. Did you figure this out, if so how?
    Honestly this question is better suited for the Dell forums, they have a number of people there that can reproduce your issue and ultimately try to solve this for you.
    http://www.enhansoft.com/

  • Dell Updates using SCUP error 0x800b0004

    Dear, 
    When trying to deploy Dell updates using SCCM (and SCUP integration) we constantly receive the following error:
    WUAHandler.log: "Failed to download update to the WUAgent datastore. Error = 0x800b0004" 
    UpdatesHandler.log: "Failed to initiate install of WSUS updates, error = 0x800b0004"
    "Failed to start WSUSUpdate, error = 0x800b0004"
    The SCUP certificate has been imported in the Trusted Root CA & Trusted publisher store on the WSUS (SCCM) server and the server we are using to test the deployment.
    Any ideas?
    Best regards,
    B.

    Just wanted to add a few things for any possible readers of this thread. 
    I have been battling SCUP 2011 and SCCM 2012 R2, pretty successfully. What I did was.
    1. Requested a cert from our internal CA per other resources that are out there.
    2. Published cert via SCUP.
    3. Added cert to Trusted Publishers folder in Cert.Manager on Windows clients in workstation context. (manually this can be done by running MMC first, then Ctrl+M and Certificates, when it opens it will prompt for context, User, Machine, Service)
    One thing that was really helpful to me was the actual Crypto API log of Windows, as it told me what was wrong with the cert I generated initially (bad chain). Run event viewer, nav to Apps and Services folder, MS, Windows, CAPI2 (I assume this stands for
    Crypto API), right-click on Operational log, and click ENABLE to start logging. The latter can greatly enhance your troubleshooting.
    Cheers.

  • Adobe Reader software updates delivered via Config Manager

    Hello. I've got a fleet of Windows 7 PCs running Reader X. I deploy software updates via Config Manager, and import the Adobe updates via SCUP. All my Windows 7 PCs are currently running version 10.1.1, however none of them are picking up Reader 10.1.3. The update just isn't being flagged as required... any ideas?
    By the way, I did look at update path and nothing jumped out at me from there

    Hello again, sorry the tardy reply.
    SCCM reqs - yes. Pretty standard setup. Flash updates roll out without any issues.
    No errors - nothing happens.
    Exact steps:
    Receive SCUP alert
    Import Adobe updates
    Publish Updates
    Synch SCCM Software Updates
    Deploy Adobe updates (as I siad, Flash updates are fine, so I don't see this as a SCUP problem).
    That said, I deleted the Adobe updates from Config Manager, and then redeployed them as part of the standard monthly release. This time I received around 2100 installs and 3200 not required (this is about right for Adobe X), whereas before I was getting double figures for installs and mostly Not Required.
    Perhaps I had received a bad update, or maybe something went wrong with the SCUP to SCCM import/packaging.
    Anyway, all sorted... thank you for the response.

Maybe you are looking for