@manny2375 said in Azure VM + Intune Autopilot:

@obsolesce thanks I know this method works unfortunately this specific client doesn’t want anything onpremise other than networking equipment and thin clients. The autopilot feature would have been nice on azure vm though.

Everything you are trying to do Microsoft is telling you not to do.

Read the last part especially:

Screenshot_20210423-164402_Edge.jpg

@Super-Sundae : Can you run Sysinternal's RegMon and patch another machine with InTune? That way you can capture the changes.
Perhaps running SysMon at the same time in case it makes changes to file permissions would help..

If you can find out what the policy changes then you should be able to revert on both machines. Hopefully 🙂

@wrx7m said in Webroot SecureAnywhere Business Replacement?:

@momurda said in Webroot SecureAnywhere Business Replacement?:

This task Manager behavior is from Webroot?
I see it occasionally; one developer in particular says it is always a problem.

https://community.webroot.com/t5/Webroot-SecureAnywhere-Complete/Task-Manager/td-p/309032

According to the most recent post in that thread (edit - the most recent post is currently 2 weeks old), a beta release fixes this issue. Being that the thread started in December of 2017, it goes to show how long it takes them to fix things.

yes, that is also what we found out, especially in Windows 10.

If you have a mac you can use apple device configurator wmby which devoces can be pre cofigured and push apps. Catch is you need to use usb cable and configure phones one by one

The Whole MDM concept isn't new to exchange (though it may be to office 365). ActiveSync for exchange has had most of these features. I think they are just promoting it hoping you will want more managment.

@scottalanmiller said:

So this interesting. We have our first desktop added into InTune that is running Windows 10 Tech Preview. In InTune it does not display as "Windows 10" as I would have expected. Instead it displays as "Windows 6.4" which is slightly confusing as the kernel is "NT 6.4" and the name is "Windows 10." Blending the two is odd.

Just found it interesting.

I've seen this behavior before - I think it was WSUS - windows 8(.1) was reported by something than it's normal name.

@Dashrender said:

@alexntg said:

@Dashrender said:

@alexntg said:

A bit on the reimaging rights. Intune with SA is a volume license. You could use the volume license media and key to reimage other computers that run the same exact product version. You could use the Win8.1 Pro media and key for other Win8.1 Pro computers. Upgrade rights are only available with SA, one device per user. Do understand that if you cancel Intune, you'd be revoking your volume license rights.

Alex,
Under the old SA in a VL setup, let's say you bought Office Pro plus with SA, when you purchased it Office 2010 was out, but during your subscription, Office 2013 comes out.
Now say you discontinue your subscription. It is my understanding that you can use 2013 in perpetuity.

Is the same true for machines that you purchase Intune with SA? So you have a Windows XP machine today, you buy Intune with SA which allows you to upgrade to Windows 8.1 Pro (or Enterprise if you wish). If you dump the SA portion of the subscription are you required to go back to XP on that computer? If that's the case, calling it SA was a bad decision as the rules would be different for two things with the same name.

The software, including the OS license, is provided on a subscription basis only. There is, however, a buyout option that's available for cancellations after the initial 12-month term. I'm not sure what the pricing on it is offhand, as that requires contacting MS directly.

Thanks - I do recall seeing something about a buyout.

Do we have a MS rep around to answer this?