Jump to content

Recommended Posts

Posted
Am currently testing sccm 2012 in a lab environment and am looking at purchasing some tablets I have read quite a bit about windows 8.1 and UEFI/EFI, has anyone succesfully got a task sequence working with UEFI/EFI that they could share some screenshots I have setup a test task sequence but dont have a unit to test it with yet and also if you have advice/tips or things to look out for when deploying OS to UEFI/EFI?
Posted
You need to make sure your Distribution Point is either on Server 2012 or 2012 R2. These are the only 2 that will allow PXE Boot on UEFI devices.
Posted
You need to make sure your Distribution Point is either on Server 2012 or 2012 R2. These are the only 2 that will allow PXE Boot on UEFI devices.

 

thansk for the fast responce, yea saw that I needed Server 2012 and SCCM 2012 SP1 which is what I have in my test environment.

Posted

Apart from that, I am not sure what else is required on UEFI.

 

If you are using Windows 8.1 you should use SCCM 2012 R2. If you use 2012 SP1 you will find you can't install drivers during OSD. The new version of Windows PE in SCCM 2012 R2 supports drivers with Windows 8.1.

Posted
Apart from that, I am not sure what else is required on UEFI.

 

If you are using Windows 8.1 you should use SCCM 2012 R2. If you use 2012 SP1 you will find you can't install drivers during OSD. The new version of Windows PE in SCCM 2012 R2 supports drivers with Windows 8.1.

 

Not true. All you need to do is create a new boot image from Windows PE 5 and add it into SCCM 2012 SP1. I've done that and I'm deploying Windows 8.1 and its drivers from 2012 SP1 just fine.

 

Your entire SCCM infrastructure does not need to be run on Windows 2012 but your PXE enabled DP does if you want to PXE boot UEFI clients.

Posted (edited)
Not true. All you need to do is create a new boot image from Windows PE 5 and add it into SCCM 2012 SP1. I've done that and I'm deploying Windows 8.1 and its drivers from 2012 SP1 just fine.

 

The key word I used is should, I didn't say it wasn't possible or was required. So what I said is correct. - FYI What you are doing is not supported according to Microsoft technical support. An upgrade is simple anyway so can't see why not to.

Edited by FN-GM
Posted
Apart from that, I am not sure what else is required on UEFI.

 

If you are using Windows 8.1 you should use SCCM 2012 R2. If you use 2012 SP1 you will find you can't install drivers during OSD. The new version of Windows PE in SCCM 2012 R2 supports drivers with Windows 8.1.

 

thanks for the feed back, do you have any screenshot of your task sequences you could share i.e how you have your drives formatted and under apply operating system how you have told sccm what partion to install to?

 

- - - Updated - - -

 

Not true. All you need to do is create a new boot image from Windows PE 5 and add it into SCCM 2012 SP1. I've done that and I'm deploying Windows 8.1 and its drivers from 2012 SP1 just fine.

 

Your entire SCCM infrastructure does not need to be run on Windows 2012 but your PXE enabled DP does if you want to PXE boot UEFI clients.

 

thanks for the feed back, do you have any screenshot of your task sequences you could share i.e how you have your drives formatted and under apply operating system how you have told sccm what partion to install to?

Posted (edited)

Because installing a cumulative update (i.e. a minor patch) to introduce Windows 8.1 support is simpler than doing a major version upgrade and requires less downtime. You do need CU3 or CU4 (I forget which) for it to work admittedly.

 

But yes, if you're starting from scratch there is no reason not to start from the latest version.

 

My task sequences are nothing special but here you go:

 

sccm.pngsccm uefi.png

 

Those are pretty close to the default settings.

Edited by Norphy
Posted
Because installing a cumulative update (i.e. a minor patch) to introduce Windows 8.1 support is simpler than doing a major version upgrade and requires less downtime. You do need CU3 or CU4 (I forget which) for it to work admittedly.

 

But yes, if you're starting from scratch there is no reason not to start from the latest version.

 

My task sequences are nothing special but here you go:

 

[ATTACH=CONFIG]24175[/ATTACH][ATTACH=CONFIG]24176[/ATTACH]

 

Those are pretty close to the default settings.

 

excellent thank you exactly how I have mine setup. just need to get a unit to test. Do you use tablets at your site if so may I ask what make and model you have?

Posted (edited)
excellent thank you exactly how I have mine setup. just need to get a unit to test. Do you use tablets at your site if so may I ask what make and model you have?

 

No tablets yet but I have some Stone laptops with SecureBoot enabled UEFIs and these work perfectly. The model is based on a Clevo W550EU chassis. I also have a desktop PC booting from UEFI, that uses an Asus H81T motherboard.

 

/edit We have ordered a Dell Venue 11 Pro to play with. Once I get it, I'll let you know how I get on.

Edited by Norphy
Posted
No tablets yet but I have some Stone laptops with SecureBoot enabled UEFIs and these work perfectly. The model is based on a Clevo W550EU chassis. I also have a desktop PC booting from UEFI, that uses an Asus H81T motherboard.

 

/edit We have ordered a Dell Venue 11 Pro to play with. Once I get it, I'll let you know how I get on.

 

Cheers.

  • 3 months later...
Posted
/edit We have ordered a Dell Venue 11 Pro to play with. Once I get it, I'll let you know how I get on.

 

Did you ever get your Dell Venue 11 Pro and manage to use SCCM to deploy an OS to it successfully?

Posted (edited)
Yes. It took a bit of tarting about with the boot image, injecting drivers etc and of course you need a USB NIC (We bought a Dell one with the tablet, their part code 0TFXX8) but once I did that it all worked perfectly. Edited by Norphy
  • Thanks 1
Posted (edited)

Ok, did you try to image more than one? We've got 64 of them and for whatever reason when trying to do an OSD SCCM will name them with the same name and then fail the process. The first tablet worked great but now its turning into a never ending nightmare :(

 

EDIT:

 

I think I've just twigged what's going wrong... I bought a handful of USB 2.0 Ethernet RJ45 Network Lan Adapters thinking I could do a batch then another batch once the previous lot had finished. I guess the OSD procedure is seeing the same MAC address from the USB adapter and automatically naming the device which is causing me issues.

Edited by jaminben
Posted (edited)
Ok, did you try to image more than one? We've got 64 of them and for whatever reason when trying to do an OSD SCCM will name them with the same name and then fail the process. The first tablet worked great but now its turning into a never ending nightmare :(

 

EDIT:

 

I think I've just twigged what's going wrong... I bought a handful of USB 2.0 Ethernet RJ45 Network Lan Adapters thinking I could do a batch then another batch once the previous lot had finished. I guess the OSD procedure is seeing the same MAC address from the USB adapter and automatically naming the device which is causing me issues.

 

 

I had the same problem with 20 Acer USB NIC Adapters

 

Create and SQL Query using the following

 

delete from System_MAC_Addres_ARR where MAC_Addresses = 'ENTER:MAC:ADDRESS'

delete from System_MAC_Addres_ARR where MAC_Addresses = 'ENTER:MAC:ADDRESS:2'

delete from LastPXEAdvertisement where MAC_Addresses = 'ENTER:MAC:ADDRESS'

delete from LastPXEAdvertisement where MAC_Addresses = 'ENTER:MAC:ADDRESS:2'

delete from Netcard_DATA where MACAddress00 = 'ENTER:MAC:ADDRESS'

delete from Netcard_DATA where MACAddress00 = 'ENTER:MAC:ADDRESS:2'

 

Enter all your MAC addresses for each 3 commands (1 per line) then run the query in SQL Management Studio against your SCCM Database.

 

Do it before and after a wave of imaging and it will remove all MAC associations.

 

I have also set the OSDComputerName variable against the collection i deploy the task sequence too. That allows me to manually enter the correct machine name.

 

Hope this helps

 

Darren

Edited by dblight
  • Thanks 1
Posted (edited)

Thanks Darren for confirming my theory. I'm not brave enough to run those commands against our database though but we do already use the OSDComputerName variable.

 

I've already created a bootable USB drive so I'll just duplicate that with an unattended file to get the job done at this point.

Edited by jaminben
Posted
Ok, did you try to image more than one? We've got 64 of them and for whatever reason when trying to do an OSD SCCM will name them with the same name and then fail the process. The first tablet worked great but now its turning into a never ending nightmare :(

 

EDIT:

 

I think I've just twigged what's going wrong... I bought a handful of USB 2.0 Ethernet RJ45 Network Lan Adapters thinking I could do a batch then another batch once the previous lot had finished. I guess the OSD procedure is seeing the same MAC address from the USB adapter and automatically naming the device which is causing me issues.

 

Ah, no, there you have me. We only have the one so far. That theory makes perfect sense too.

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...