[mssms] 1 Microsoft Ignite Pass - Needed

[Nick sullivan]

After long justification with are management team, we have been approved to 
attend Microsoft Ignite 2017.  Unfortentey we must pay out of pocket.  I'm 
looking for anyone with extra passes or companys that are giving away passes in 
exchange for Software Demo's which could lead to potential sales.  I work for a 
large healthcare system in the midwest with over 30K nodes.  I apoligize for 
the spam.


Thanks Guys,

[mssms] RE: MBR2GPT question

[Richard Poole]

I’m pretty sure that’s not what’s going on with these systems, since a cursor 
is all I get after rebooting a system converted from MBR to GPT. I even booted 
into a WinPE stick, sans SCCM, ran MBR2GPT manually, and still get the problem 
upon reboot, which is why I can’t think it’d have anything to do with the task 
sequence. Granted, I do get that cursor problem in OSD and glad to have a 
solution to it, but this is something more akin to the original Win10 technical 
preview where the login screen is just black but moving the mouse makes the 
cursor appear for a second.

Thanks for the assist, though!

Thank you,
Richard Poole

From: listsad...@lists.myitforum.com [mailto:listsad...@lists.myitforum.com] On 
Behalf Of Troy Martin
Sent: Thursday, August 10, 2017 2:24 PM
To: mssms@lists.myitforum.com
Subject: [mssms] RE: MBR2GPT question

https://blogs.technet.microsoft.com/system_center_configuration_manager_operating_system_deployment_support_blog/2017/02/23/no-mouse-cursor-during-configmgr-osd-task-sequence/

Troy L. Martin | Technical Architect
1E | Software Lifecycle Automation for the Digital Business
US Mobile: +1 (678) 898-6147 | UK Phone : +44 208 326 9141
troy.mar...@1e.com | 
www.1e.com

Facebook
 | 
Twitter
 | 
YouTube
 | 
Blogs
 | 
RSS

From: listsad...@lists.myitforum.com 
[mailto:listsad...@lists.myitforum.com] On Behalf Of Richard Poole
Sent: Thursday, August 10, 2017 2:31 PM
To: mssms@lists.myitforum.com
Subject: [mssms] MBR2GPT question

Hey everyone,

I’ve been playing around with MBR2GPT on a Win10 1703 build and keep running 
into a strange issue. No matter if I run it from the OS with /allowFullOS or 
within WinPE, and change the BIOS over to UEFI, upon booting into Windows I get 
a black screen. Mouse cursor shows up when I move it, and promptly disappears. 
I’ve tried on a laptop and two desktops, with various displays, hit Win+P+down 
arrow to try and switch displays, all experienced the same issue.

Anyone else seen this problem by chance?

Thanks,
Richard Poole


NOTICE: This message contains confidential information and is intended only for 
the individual named. If you are not the named addressee, you should not 
disseminate, distribute or copy this email. Please notify the sender 
immediately by email if you have received this email by mistake and delete this 
email from your system. Email transmission cannot be guaranteed to be secure or 
error-free, as information could be intercepted, corrupted, lost, destroyed, 
arrive late or incomplete, or contain viruses. The sender, therefore, does not 
accept liability for any errors or omissions in the contents of this message. 
This email neither constitutes an agreement to conduct transactions by 
electronic means nor creates any legally binding contract or enforceable 
obligation in the absence of a fully signed written contract.





Legal Notice: This email is intended only for the person(s) to whom it is 
addressed. If you are not an intended recipient and have received this message 
in error, please notify the sender immediately by replying to this email or 
calling +44(0) 2083269015 (UK) or +1 866 592 4214 (USA). This email and any 
attachments may be privileged and/or confidential. The unauthorized use, 
disclosure, copying or printing of any information it contains is 

[mssms] RE: Patch Deployment Device Restart Behavior

[Tim Amico]

Create a collection with a maintenance window for every Saturday and Sunday 
then place your critical servers or all servers in the collection. You can set 
it for all deployments or just Software updates and this way the servers will 
do nothing during the week unless you manually kick something off in Software 
Center.

From: listsad...@lists.myitforum.com [mailto:listsad...@lists.myitforum.com] On 
Behalf Of Matt Gerding
Sent: Monday, August 14, 2017 8:40 AM
To: mssms@lists.myitforum.com
Subject: [mssms] Patch Deployment Device Restart Behavior

Hello,

I was hoping to get some feedback for what people are doing to suppress reboots 
for Windows patch deployments via SCCM. More specifically, if your patch 
deployment is scheduled, specified as "Required" with no device restart 
behavior suppression set, how do you stop a client machine or a server from 
forcefully restarting?

In our environment we create separate monthly patch deployments for clients and 
servers. We set a system restart suppression for workstations when deploying 
patches to our clients, so user machines never forcefully reboot. However, for 
our server environment, we do not set any suppression because we don't want to 
manually reboot all of the 100 + servers. I schedule the server patch 
deployments on the weekends, and we rarely have issues, but we've seen a couple 
random servers that have downloaded the patches but for whatever reason the 
servers don't reboot over the weekend. When I come in on Monday, I'll check the 
status of the servers and find that these random servers are still "In 
Progress", and then these servers will forcefully reboot mid-day.

In a situation where the server(s) in question are critical system servers, and 
are attempting to reboot mid-day, people obviously freak out. Is there a way to 
override this so I don't have a server rebooting mid-day?


Regards,

Matthew Gerding
Information Technology
Centurion Medical Products
517.540.1618
www.centurionmp.com
*
PATIENT CARE WITHOUT COMPROMISE(tm)

Re: [mssms] Patch Deployment Device Restart Behavior

[Adam Juelich]

You control that with Maintenance Windows.

On Mon, Aug 14, 2017 at 7:40 AM, Matt Gerding 
wrote:

> Hello,
>
>
>
> I was hoping to get some feedback for what people are doing to suppress
> reboots for Windows patch deployments via SCCM. More specifically, if your
> patch deployment is scheduled, specified as “Required” with no device
> restart behavior suppression set, how do you stop a client machine or a
> server from forcefully restarting?
>
>
>
> In our environment we create separate monthly patch deployments for
> clients and servers. We set a system restart suppression for workstations
> when deploying patches to our clients, so user machines never forcefully
> reboot. However, for our server environment, we do not set any suppression
> because we don’t want to manually reboot all of the 100 + servers. I
> schedule the server patch deployments on the weekends, and we rarely have
> issues, but we’ve seen a couple random servers that have downloaded the
> patches but for whatever reason the servers don’t reboot over the weekend.
> When I come in on Monday, I’ll check the status of the servers and find
> that these random servers are still “In Progress”, and then these servers
> will forcefully reboot mid-day.
>
>
>
> In a situation where the server(s) in question are critical system
> servers, and are attempting to reboot mid-day, people obviously freak out.
> Is there a way to override this so I don’t have a server rebooting mid-day?
>
>
>
>
>
> Regards,
>
>
>
> *Matthew Gerding*
>
> Information Technology
>
> Centurion Medical Products
>
> 517.540.1618 <(517)%20540-1618>
>
> www.centurionmp.com
>
> •
>
> *PATIENT CARE WITHOUT COMPROMISE™*
>
>
>
>

[mssms] Patch Deployment Device Restart Behavior

[Matt Gerding]

Hello,

I was hoping to get some feedback for what people are doing to suppress reboots 
for Windows patch deployments via SCCM. More specifically, if your patch 
deployment is scheduled, specified as "Required" with no device restart 
behavior suppression set, how do you stop a client machine or a server from 
forcefully restarting?

In our environment we create separate monthly patch deployments for clients and 
servers. We set a system restart suppression for workstations when deploying 
patches to our clients, so user machines never forcefully reboot. However, for 
our server environment, we do not set any suppression because we don't want to 
manually reboot all of the 100 + servers. I schedule the server patch 
deployments on the weekends, and we rarely have issues, but we've seen a couple 
random servers that have downloaded the patches but for whatever reason the 
servers don't reboot over the weekend. When I come in on Monday, I'll check the 
status of the servers and find that these random servers are still "In 
Progress", and then these servers will forcefully reboot mid-day.

In a situation where the server(s) in question are critical system servers, and 
are attempting to reboot mid-day, people obviously freak out. Is there a way to 
override this so I don't have a server rebooting mid-day?


Regards,

Matthew Gerding
Information Technology
Centurion Medical Products
517.540.1618
www.centurionmp.com
*
PATIENT CARE WITHOUT COMPROMISE(tm)