ok can you please go through this workflow and see does it help

https://docs.microsoft.com/en-us/sccm/core/servers/manage/download-updates-flowchart

On Tue, Jan 10, 2017 at 10:51 PM, Magnus Tveten <[email protected]>
wrote:

> Yup I did try that… but tried again now got good measure.. no luck..
>
>
>
>
>
> *From:* [email protected] [mailto:listsadmin@lists.
> myitforum.com] *On Behalf Of *Niall Brady
> *Sent:* Tuesday, 10 January 2017 4:49 PM
> *To:* [email protected]
> *Subject:* Re: [mssms] 1610 update issue
>
>
>
> have you tried restarting smsexec ?
>
>
>
> On Tue, Jan 10, 2017 at 4:36 AM, Magnus Tveten <[email protected]>
> wrote:
>
> HI All,
>
>                 In my Lab SCCM environment I seem to have an issue with
> the 1610 update replicating from the CAS(yes I know...it just ended up we
> needed a CAS) to the primary server.
>
>
>
> (yes I also realise that this happened quite some time ago now.. but the
> update just popped up on prod recently as available and that made me think
> to check in lab)
>
>
>
> My problem is that there does not seem to be any way to make it retry….
> The Distmgr.log has nothing relevant to this anymore,
>
> Docs seem to indicate I should be able to retry..
>
> https://github.com/Microsoft/SCCMdocs/blob/master/sccm/
> core/servers/manage/install-in-console-updates.md#bkmk_retry
>
> however there is no re-try.. only run Prerequisite check.
>
>
>
> Anyone seen this happen and have any ideas for a fix ?
>
>
> ------------------------------
>
> *Magnus Tveten*
>
> *Server Engineer*
>
> Infrastructure oN demand
> IAG labs
>
>
> _____________________________________________________________________
>
> The information transmitted in this message and its attachments (if any)
> is intended
> only for the person or entity to which it is addressed.
> The message may contain confidential and/or privileged material. Any
> review,
> retransmission, dissemination or other use of, or taking of any action in
> reliance
> upon this information, by persons or entities other than the intended
> recipient is
> prohibited.
>
> If you have received this in error, please contact the sender and delete
> this e-mail
> and associated material from any computer.
>
> The intended recipient of this e-mail may only use, reproduce, disclose or
> distribute
> the information contained in this e-mail and any attached files, with the
> permission
> of the sender.
>
> This message has been scanned for viruses.
> _____________________________________________________________________
>
>
>
>
>
>
>
> _____________________________________________________________________
>
> The information transmitted in this message and its attachments (if any)
> is intended
> only for the person or entity to which it is addressed.
> The message may contain confidential and/or privileged material. Any
> review,
> retransmission, dissemination or other use of, or taking of any action in
> reliance
> upon this information, by persons or entities other than the intended
> recipient is
> prohibited.
>
> If you have received this in error, please contact the sender and delete
> this e-mail
> and associated material from any computer.
>
> The intended recipient of this e-mail may only use, reproduce, disclose or
> distribute
> the information contained in this e-mail and any attached files, with the
> permission
> of the sender.
>
> This message has been scanned for viruses.
> _____________________________________________________________________
>
>



Reply via email to