Jump to content

Recommended Posts

Posted (edited)

Hello all,

I've just got access to InTune but I have fallen at the first hurdle and can't do anything. I naively thought there would be an msi or exe I could run on a computer and after a moment, it would appear as a device however this does not appear to be the case. I've tried "signing on with a school account" but I get met with random error messages.

I've been stuck staring at random Microsoft articles and am not sure if I should concentrate on the error message, install the AD connector for InTune or do something completely different. I've not even looked at autopilot yet until I can get at least something going.

 

Bit disheartened by the whole thing as I was eager to get going.

 

Really I'd be chuffed to bits if I could just get a device attached so I can start testing settings.

 

Just looking for a direction to get started really (or just a pointer on how to get a device to show up).

 

Thanks all

 

[Edit: I should say I'm using the Endpoint Intune. I'm licenced for Education but only interested in the full product as I'm interested in the security and software management of remote clients]

Edited by robjduk
  • 1 month later...
Posted (edited)

 

Just looking for a direction to get started really (or just a pointer on how to get a device to show up).

 

Not the direct thrust of the article but look at https://itsalwaysmyproblem.com/2018/08/23/tuning-up-intune-self-service-password-reset-from-the-login-screen/ - touches on the high points - devices and users need to be visible in Azure AD so that they can be onboarded into Intune, etc.

Edited by Roberto
  • Thanks 1
  • 1 month later...
Posted

I've got Intune/Autopilot mostly working, but I definitely need to do more testing before moving to production.

 

I've seen lots of guides for building labs with Hyper-V VMs, but after finding that failed, the information on the web pointed to the instructions which state that VMs aren't supported as you need TPM 2 for it to work. You can enable TPM in the Hyper-V Manager machine settings, but that doesn't seem to satisfy Autopilot.

 

Is it possible to set up a lab with VMs?

Posted
I've got Intune/Autopilot mostly working, but I definitely need to do more testing before moving to production.

 

I've seen lots of guides for building labs with Hyper-V VMs, but after finding that failed, the information on the web pointed to the instructions which state that VMs aren't supported as you need TPM 2 for it to work. You can enable TPM in the Hyper-V Manager machine settings, but that doesn't seem to satisfy Autopilot.

 

Is it possible to set up a lab with VMs?

 

Not sure about Hyper-V, but autopilot does work with VMware VMs (on VMware Workstation at least). I've got 5 or 6 VMs running a mix of W10/11, with a mix of TPM for testing bitlocker and others without. The only things I've found not supported with VMs are the white glove part of Autopilot and self-deploying mode.

Posted
Not sure about Hyper-V, but autopilot does work with VMware VMs (on VMware Workstation at least). I've got 5 or 6 VMs running a mix of W10/11, with a mix of TPM for testing bitlocker and others without. The only things I've found not supported with VMs are the white glove part of Autopilot and self-deploying mode.
It was the self-Deployment and white glove (pre-provisioned) I was hoping to test more.

 

Do you generally find it fussy? I had a single Dell laptop that I was using as a test machine. Spent hours trying to work out why it wouldn't go into assigned status on Monday, logged into Autopilot console on Tuesday morning and it was there. Then spent ages trying to get it to provision and it wouldn't reliably pick up network (which is why I wanted VMs, so that I could exclude hardware issues), then it picked up the organisation and knew what profile it had assigned, but kept failing to deploy. I ran out of time until yesterday, when I just turned it on and it worked. So I have it working, but I don't know why it sometimes doesn't.

Posted (edited)
It was the self-Deployment and white glove (pre-provisioned) I was hoping to test more.

 

Do you generally find it fussy? I had a single Dell laptop that I was using as a test machine. Spent hours trying to work out why it wouldn't go into assigned status on Monday, logged into Autopilot console on Tuesday morning and it was there. Then spent ages trying to get it to provision and it wouldn't reliably pick up network (which is why I wanted VMs, so that I could exclude hardware issues), then it picked up the organisation and knew what profile it had assigned, but kept failing to deploy. I ran out of time until yesterday, when I just turned it on and it worked. So I have it working, but I don't know why it sometimes doesn't.

 

I must remove the 365 app from my phone (now using google workspace :() but earlier in the week, I kept getting lots of service issues with intune/autopilot popping up which sounds about the same time you were seeing delays.

 

 

Honestly, I really like intune/MEM with windows. Some things took me a while to adjust to (Win32 application packaging/custom settings profiles etc) but it does eventually do what you configure. I'm used to things taking a while from SCCM (or Systems Management Server as it used to be called...slow moving software) but when autopilot works it's absolutely fantastic. I did find it tricky/fussy when first setting it up but most of the stuff I did then, like custom OMA-URI/CSPs, are now in the settings catalog feature from the intune UI.

 

Edit: found one of the issues that may have impacted you - https://support.nhs.net/2022/05/microsoft-365-alert-service-degradation-microsoft-intune-users-may-be-intermittently-unable-to-use-autopilot-to-set-up-their-devices/

Edited by computer_expert
  • Thanks 1

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now



×
×
  • Create New...