https://bugs.documentfoundation.org/show_bug.cgi?id=155408

Mike Kaganski <mikekagan...@hotmail.com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|UNCONFIRMED                 |RESOLVED
         Resolution|---                         |NOTOURBUG

--- Comment #30 from Mike Kaganski <mikekagan...@hotmail.com> ---
(In reply to Adam Clarke from comment #29)

Thanks for the update.

> We don't have the ability to open a ticket with Microsoft with our schools
> agreement type so this is not an option for us im afraid.

Too bad...

> I have imported
> the latest VcRedist into SCCM using vcredist.com but it just fails to
> install in the task sequence with an unspecified error.

It looks very pathetic on the SCCM side, and suspiciously related to the issue
here - note how SCCM struggles to deploy the suspected MS system component
update, packaged by MS themselves... Honestly, *for now* it truly looks like a
bug (or some misconfiguration) in SCCM.

> I think I am going
> to have to deploy an older version this year 7.3.0.3 as I know that works
> which is a shame but I am in a position where I need to deploy my new image
> pretty urgently now so although I am keen to get a resolution the need to
> deploy the image is greater for me. I really appreciate all your help on
> this but I realise you cannot simply roll back the change either.

You are right: the change between the versions happened because MS (again MS!
:D) released an update to their Visual Studio; and many (most) of their updates
include security fixes - which means, that not updating not only puts our
builder in danger, but -more importantly - may put the users in danger, if they
use programs compiled using unfixed compiler. We need some clear resolution
here.

> Unfortunately it just means that deployment for the time being with
> Microsoft Endpoint Configuration Manager or the Microsoft Deployment Toolkit
> will not be possible with the latest versions.

Sorry for that; let me close it as NOTOURBUG - but feel free to reopen, if you
happen to get a new bit of useful information.

-- 
You are receiving this mail because:
You are the assignee for the bug.

Reply via email to