TechyGeeksHome

SCCM OSD Policy Retrieval Error
If you are using System Center Configuration Manager for Operating System Deployment (OSD) then you may come across an error like this even after a successful PXE boot:


You will find that this is because the machine will not display its task sequences as it cannot retrieve the policies to do this.

The reason for this is that the date and/or time on the target machine is incorrect and needs to be in sync with the SCCM server.

You will need to go into your BIOS settings and check both the date and time settings to ensure that they are correct. Once you have corrected this, try to PXE boot the machine and you should now find that it works and will start to display your task sequences.

COMMENTS

If you have any questions or comments on this guide, please feel free to leave us a message below using our Disqus system.

Labels: , , , ,

Windows and Office Activation Proxy Whitelist Websites
We recently came across an issue where our Configuration Manager Operating System Deployments (OSD) were failing at the activating Windows step. Having spent far too much time looking into why it was doing this, we eventually found out that it was our proxy servers that were blocking access it the Microsoft activation servers.

So, to get around these issues, we have acquired a list of websites that need to be whitelisted to enable Windows activation to work so add these to your own whitelists if you are having a similar problem:
After this, we also found that we had a similar issue with our Office activation's. So, there are also a few other websites that you should add to your whitelists to cover Office as well:
COMMENTS

If you have any questions or comments on this post, please feel free to leave us a message below using our Disqus system.

Labels: , , , ,

Windows Live Meeting MSI Installer Download
If you have users that are still using Windows Live Meeting, you may want the MSI installer to be able to distribute it through Group Policy, WDS or Configuration Manager.

So, we have extracted the MSI from the main installer and made it available on our downloads microsite under the Windows category.

DOWNLOAD

Visit our downloads microsite by clicking the download button below to get the Windows Live Meeting MSI Installer.


INSTRUCTIONS

If you want to distribute this MSI file you can use the following command lines:

 msiexec.exe /i "lminstall.msi" /passive /norestart  

COMMENTS

If you have any questions or comments on this, please feel free to leave us a message below using our Disqus system.

Labels: , , , , , , ,

SCCM OSD - "A required device isn't connected or cannot be accessed"
We today ran into an issue where our SCCM OSD PXE boot was not working. It was coming up with a very confusing message stating:

"A required device isn't connected or cannot be accessed"


This led us to start looking at the hard drive and the drivers, however, the solution was completely different.

The problem was that the RamDiskTFTPBlockSize we were using on our distribution point was too high, so we had to lower it to the Microsoft default.

To do this, you should follow these steps:

You should then retry your PXE boot sequence and you should find that it now works.

COMMENTS

If you have any questions or comments on this guide then please feel free to leave us a message below using our Disqus system.

Labels: , ,

How to identify a missing NIC driver during SCCM OSD
If you have a new model of computer and you have PXE booted it and you do not get a network connection or IP address, then this is because the network card driver for that model is not available either within Windows PE or the boot image you have used to PXE boot the machine.

To fix this can be very difficult as you have to identify the correct the model of the network card, then download the correct driver, test that driver within Windows PE, then once you have got the correct driver, you have to import it into SCCM and then inject into your boot image.

To do this, you first have to PXE boot the affected computer and once into Windows PE, press F8 quickly to start a command prompt. To ensure that you are looking at the correct problem, type in IPConfig and press enter. You should find that if it is a network card error, you are receiving no IP address. If this is the case, you should now take steps to identify the network card.

Whilst in your command prompt, you will need to run the WMI test tool, you can do this by typing in WBEMTEST and it will bring up a box like this:


You should then click the Connect button and connect to the following location:

root\cimv2

This will enable all the other buttons and now allow you to click the Query button:


You then need to enter a query to identify the hardware details of your network card. The query you should run is:

Select * from Win32_PNPEntity where description LIKE "%ether%"

You should then click the Apply button:


This will then bring up the Query Result dialogue box and will look similar to this:


You should then double click each result (most cases there will only be one result but we have Hype-V installed on our test machine so there is two..) and it should bring up a box like this:


In the Properties window space, you should scroll down and then look for two things to identify the network card. One is the “Caption” and the other is the DeviceID:



You have then identified the network card driver that is required. But there is now also a simple way of getting that driver. If you take a copy of the DeviceID, you should then go to the Windows Update Catalog which is here:

https://catalog.update.microsoft.com

You can then enter the DeviceID into the search and download the required driver.

Once you are happy that you have the correct driver, copy the driver files to a memory stick and plug it into the machine with the issue.

You should then go back to your command prompt and browse to the location of the network card drivers on the memory stick. Then, you should run the following command:

Drvload “networkcarddriver.inf” (being whatever the name of the network card driver inf is)

When it has loaded, you should then type in IPConfig – if you get an IP address, you have the correct driver and you can then import it into SCCM and add to your boot image.

If you do not get an IP address, you have the incorrect driver and you should find another one.

REMEMBER – you are getting the driver for the Windows PE version you are using, not the Windows Operating system you are hoping to install.

COMMENTS

If you have any questions or comments on this guide then please feel free to leave us a message below using our Disqus system.

Labels: , ,

SCCM 2012 Client Stuck in Provisioning Mode
We recently have had issues with our Windows 7 operating system deployments seemingly not completing fully.

We were getting the following issues:
The client control panel applet looked like this:


After going through various logs and searching the internet, we found that the problem was that after the client install during the task sequence, after a reboot from WinPE into Windows, the client itself was getting stuck in provisioning mode - a bit like a evaluation mode for the client so when into the main windows operating system, it will not function correctly.

So, how can it be fixed?

The problem is two registry keys that need to be amended after the client installation during the task sequence. So, immediately after the client installation step in your task sequence, you should create two Run Command Line steps. In the first step, you should call it "Turn off provisioning mode" and for the command line enter the following:

 REG ADD HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\CCM\CcmExec /v ProvisioningMode /t REG_SZ /d false /f  

So your first step should look like this:


For your second command line step, you should call it "Turn off System Task Excludes" and for the command line enter the following:

 REG ADD HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\CCM\CcmExec /v SystemTaskExcludes /t REG_SZ /d "" /f  

So your second step should look like this:


Once you have made these additions then save your task sequence and try another deployment, you should now find that this works perfectly!

If you also have a machine that is affected by this problem and do not want to re-image the machine, you can simply make these changes in the registry manually in Windows, reboot the machine and you should then find that the client will work.

COMMENTS

If you have any comments or questions, please feel free to use our Disqus system below.

Labels: , ,

ConfigMgr OSD Boot Image Problems with Dell Machines
With the recent release of Dell's new laptop ranges, Configuration Manager OSD professionals face new challenges. We recently had issues with some of Dell's new laptops not picking up the network after PXE boot even though we had gone through the normal process of adding the network card drivers to the boot image and ensuring it was the correct driver etc etc.

The models in question that we were having a problem with were the Dell Latitude E6540 and the Dell Latitude E7240. So, how did we fix it? the answer is extremely simple - we ignored Dell!

We had downloaded the Driver Packages from the Dell Support website for both of these models and loaded the drivers into our Configuration Manager environment as we have done for many machines in the past. But, unusually for WinPE v4 (which we are currently using with Configuration Manager 2012 SP1) the machines would not pick up the network after the PXE boot had taken place. So, we added the correct network card drivers to the boot image for each machine and tried again - still not picking up the network.

This was driving us mad for quite some time, until someone in our office told us to try the Intel website direct for the latest drivers. So, we did! we downloaded the two Intel Pro network card packs and loaded them into our Configuration Manager. We then selected the correct drivers for the machines from this new driver package and added them to the boot image instead.

Having redistributed our boot images, the two machines PXE booted and picking up their network without issue at all.

So - what was the actual problem? having looked into the network card driver versions, the drivers for the Intel network cards supplied from Dell through their own support website for these model of laptops, were so far out of date, they did not work in WinPE version 4! This is terrible from Dell for new release of models and we urge them to update their drivers on their support site as soon as humanly possible. This sort of shoddy work makes our jobs extremely difficult and time consuming.

So what if you are having the same problems? well, we have kindly placed the link for the very latest network card drivers from Intel below so you can download these, add as a driver package to your Configuration Manager environment and then pick and choose which drivers you need to add to your boot images.

DOWNLOADS

Intel Network Drivers x86 & x64

COMMENTS

If you have any comments on this or just want to thank us, then please leave a comment below using our Disqus system.

Labels: , , ,

Windows XP Setup Please Wait - Configuration Manager OSD on Dell Laptops
We have recently been tasked with fixing a problem with Configuration Manager 2012 SP1 and deploying a fat Windows XP wim image to a Dell Latitude E5510 with the newer generation of Intel processors, in this case the processor was an Intel i3 Processor.

The problem was this, the customer had a fat Windows XP wim image with everything loaded into it, including Office 2010 and a number of customer applications. The image file has been deployed to a whole range of older laptops including Dell D-Series and early release E-Series (like the E5500) and has always worked perfectly well. This has also included the older E5510 laptops with the earlier generations of Intel processors. However, now trying to load the same image on to a slightly newer E5510 with Intel i3 Processors, the image was not fully loading.

The Operating System Deployment (OSD) task sequence would go through the normal steps until after the machine had rebooted into Windows setup part of the sequence. Then, it would get "stuck" at the Windows XP Setup - Please Wait... screen and it would never move from there.


So, what is the problem? There are a number of factors to take into consideration with slightly newer hardware and the deployment of Windows XP. Now, this is a bit of a disclaimer - the way that we have fixed this particular problem worked for this image, with this hardware, for this customer - it may not be the "best practice" way of doing things and it may not work for you, but it is something to consider and possibly try for yourselves if you are fully out of ideas! However this did work fully for us in this case...

First of all, we noticed that the E5510 had a BIOS version of A07 - having checked the Dell Support website we found that the E5510 models latest BIOS was A16. A lot of people and IT Departments under estimate the importance of keeping BIOS versions fully up to date - I would never try and diagnose a machine without ensuring that it was on the latest BIOS version first.

So, we had to upgrade the E5510 to the latest BIOS version - simple right? well no, you cannot just upgrade to A16 from anything less than A10 and you cannot upgrade to A10 from anything less than A09! But they would be easy to find surely? well no! The Dell Support website only seems to have A11 and onwards for the E5510. So we had to go searching for A09 and A10 whilst we downloaded the A16 latest BIOS from Dell.

Now, to help those looking for these files, we will post a direct link to these two elusive Dell BIOS updates below:

DELL LATITUDE E5510 BIOS UPDATES

A09 BIOS UPDATE LINK

A10 BIOS UPDATE LINK

Once you have loaded these two BIOS updates in sequence (A09 first then A10!) you can then download from the Dell Support website the A16 (this is the latest version at time of writing this post) and load this onto your E5510 laptop.

So great, we now have the latest version of the BIOS on the machine - but that still does not solve all our problems. Having then looked into the customers drivers setup, we found that the drivers they were using for the E5510 were around 18 months out of date - including the fact that they did not have the correct drivers for the SATA, AHCI or NIC. We needed to get all the latest drivers for the E5510, so we went back to the Dell Support website for the E5510 and downloaded every single latest version of the drivers for this device and loaded them into Configuration Manager and prepared them for use with the Windows XP task sequence deployment.

Having done all of this, we re-run the OSD TS on the E5510 with the Intel i3 Processor and it ran all the way through to the end and worked perfectly!

So, as an overview, if you are having problems like this, it is always worth checking the following:
BUT WAIT! There is still one more thing that can cause you problems with an Windows XP deployment. Choosing SATA,  RAID or AHCI. We have seen in the past machines having had Windows XP deployed to them constantly blue screening on boot up - this has been due to the BIOS having RAID or AHCI set - change it to S/ATA, reload the image and see what happens - it should work!

COMMENTS

If you have any comments or further suggestions or just want to thank us! Please leave a comment below using our Disqus system.

Labels: , , , , ,

OS deployment monitoring in ConfigMgr 2012
If you are using Configuration Manager 2012 for Operating System Deployment (OSD) - which is one of the main functions of the system so we will assume that you are - then you may want to monitor the process of your task sequences.

To do this, you should go into your Configuration Manager Console and click on the Monitoring tab:


Then from the tree, you should click onto the Deployments option which will bring up all of your Configuration Manager deployments - including your Task Sequences:


You can then use the Search function to enter the name of your Task Sequence that you want to monitor:


Once you have highlighted the Task Sequence that you want to monitor, you will see an area called "Completion Statistics" and a pie chart. In that area, you will also see a View Status link:


Click this View Status link and you will be presented with the following tabs:
These are pretty self explanatory so all you need to do is click the tab (if you are looking for a running task sequence click "In Progress") you want and then you will see the Deployment ID's, highlight the one you want and it will give you the machines that are currently running (I've blanked out our computer names on the screen prints):


When you highlight the Device name it will bring up the More Details link on the right hand side, you should now click this for more detailed information on the task sequence:


This will then bring up a dialogue box and you can click the Status tab on this box for a more detailed breakdown of the progress of the task sequence:


For failed task sequences, this detailed information status will give you an indication of why the task sequence failed and at what step.

If you have any questions about this, please leave a comment below using our Disqus system.

Labels: , ,

Updating a WIM Image File using Offline Updates
If you have custom build images that you are using in your SCCM OSD environment, you may find that keeping them up to date is a real problem. However, there is a way of running Windows Updates against your custom WIM files offline and then simply redistributing your WIM file.

Below is a guide on how to carry this out and a list of downloads that you will require.

DOWNLOADS

WSUS Offline Tool

Windows Automation Installation Kit for Windows 7

INSTRUCTIONS

Download the WSUS Offline Tool from the link above and extract the zip file to a directory on your computer - for this guide purposes, we'll use "D:\WSUS" (although most people will use a C: drive location).


Run the "UpdateGenerator.exe" file located in the root of extracted files.

You will be presented with a program and you can select the versions of Windows, Office and Legacy products that you wish to update. Remember to include (or exclude) the x86 and x64 versions if you want to update these different architectures.


You also have the option to use a WSUS server on your local network to retrieve the Windows Updates from (this is much quicker if you have a slower internet connection). To do this, click the WSUS button at the bottom and enter the URL of your WSUS server:


Once you have selected all the options that you want to download updates for, press the Start button at the bottom left. A command box will appear and will start to download all the required update - this can take a long time depending on your selections and internet speed. These updates will be copied into the folder structure of the extracted files ("D:\WSUS").

Please note that although the first set of downloads will take a while, you can then run this process again at a later date and it will only download any newer updates required.

Once all your updates have been downloaded, you should then continue with the next stage of the process.

Download the Windows Automated Installation Kit for Windows 7 from the link above and install on your machine. This will install a file called "DISM.exe" - this is a command line program that we will use to mount the WIM, inject the updates and then unmount the WIM file.

You should then copy your custom WIM file to a location on your machine, for this guide, we'll use "D:\WIM".

You then need to create a temporary directory that will be used to mount the WIM image, we'll go ahead and use "D:\WIMTEMP".

You then need to open an elevated administrative command prompt and then run the following command to mount the WIM file to your earlier created temporary location:

 dism /mount-wim /wimfile:D:\WIM\wim.wim /mountdir:D:\WIMTEMP /index:2  


Please remember to change "wim.wim" to the name of your own custom WIM file.

The index:2 part of the command at the end is very important as this is the index number of the image you will be mounting. You can ensure you are using the correct index number by running the following command:

 dism /get-wiminfo /wimfile:D:\WIM\wimname.wim  


Once you have mounted your custom WIM, you then need to go into the correct directory within your earlier downloaded updates for your WIM file. So, if your WIM file is Windows 7 x64, you should go to:

 D:\WSUS\client\w61-x64\glb  

When you are in the correct working directory, run the following command:

dism /image:"D:\WIMTEMP" /Add-Package /PackagePath:"D:\WSUS\client\w61-x64\glb"  

This command will step through each update file in the directory, adding the update to the currently mounted WIM file.


When this has completed injected all the required updates into your custom WIM, you should then run the following command to commit the changes and unmount the WIM image.

 dism /unmount-wim /mountdir:D:\WIMTEMP /commit  

This will go through the unmount process and commit the updates to your custom WIM. This can then be redistributed using your SCCM environment.

If you have any problems with this, please leave a comment below.

Labels: , , ,

Windows Updates during SCCM OSD from Replica WSUS Servers
I have been asked to provide a solution to a situation where during SCCM OSD, they want to run Windows Updates across multiple sites worldwide using the local WSUS replica servers.

So as an example, the main Headquarters office is in New York with the main WSUS server and then in Rome there is another site with a replica WSUS server syncronising from the New York server. A new PC is shipped to Rome and takes the SCCM OSD deployment and they want Windows Updates to run from the Rome WSUS server to fully patch the machine to corporate WSUS standards.

Note that SCCM SUP is not used in this environment.

PREREQUISITES 

Please note that this guide assumes that you have an advanced knowledge of SCCM, WSUS and MDT.

You must also have MDT integrated in your environment for this to work.

INSTRUCTIONS

So, where do we start? Firstly, you need to identify all the WSUS servers available for each site. For demo purposes, we are going to be using the following sites and WSUS server URL's:
Once you have all the information you require you then need to export the certificate for WSUS from the primary HQ server and put it into a source share as we will be creating a package using this later. Lets create a share called:

 \\nyc-cmsource-1\OSD\WSUS  

Once you have your WSUS certificate in this share, you also need to add a registry file, this will be used to allow local updates to be published to the client machine. I have already prepared this registry file for you and this can be downloaded from the link below:

Download WSUS Registry Edit

So you should now have a registry file and a WSUS certificate in your source share. You now need to create a package within SCCM using this source share as your source location for the package. We'll call the package WSUS Certificate Import:


You then need to create three different programs using this package. One to import the certificate into the Trusted Publisher, one to import the certificate intot he Trusted Root and one to run the registry edit file to enable local updates to run.

You should use the following commands for each program:
  • Import AcceptTrustedPublishedCerts - Regedit.exe -s wsuspolicy.reg
  • Install Trusted Publisher - certutil.exe -addstore -f TrustedPublisher WSUS.cer
  • Install Trusted Root - certutil.exe -addstore Root WSUS.cer
So you should end up with a package with these three programs available from it:


Please note that you must ensure that you have selected "Allow this program to be installed from the Install Package task sequence without being deployed" on the Advanced tab of the program for this to work:


You should then distribute this package to your required distribution points so it is ready to use.

When you have completed the package and programs part, you can then move onto the task sequence steps. In this demo I'll just be showing you the steps for the updating part, however, in a live environment, I strongly suggest that you make these steps the very last part of your task sequence.

TASK SEQUENCE STEPS

In your task sequence there are five stages to getting the updates to install from the local WSUS:
  • MDT Toolkit Package
  • Import of certificates
  • Registry edit to enable local updates
  • Pointing to correct local WSUS server
  • Running of updates
So, the first part of your task sequence steps needs to be to load the MDT Toolkit:


You should then add the Trusted Root Certificate from the package and program we created earlier:


Then add the Trusted Publisher Certificate:


Then add the registry edit file:


The next set of steps are to add the variables for which local WSUS server to use. So, add a Set Task Sequence Variable step, give it a name for your local WSUS server (in our case it'll be NYC, Rome & Tokyo), then for each step the Task Sequence Variable should be:

 WSUSServer  

Then each steps value should be the local WSUS servers URL (as stated at the beginning of this guide):




Now, this is the critical part, before we move away from these steps, you need to add an option condition to each of the Task Sequence Variable steps to identify when the variable is to be used. Although there are other ways, I am going to use the AD Site Name to identify where the client machine is at. So, click on the step for Rome, then click Options:


Click the Add Condition button and select query WMI. You should then type in the following query to identify that if the client machine matches this query, this step will be activated:

 SELECT ClientSiteName FROM Win32_NTDomain WHERE ClientSiteName = "Rome"  


You should do this for each Task Sequence Variable step.

Then, the final part is to actually run the Windows Updates, this is the final step that should be run as a command line.

The command line that should be run is the following:

 cscript.exe "%SCRIPTROOT%\ZTIWindowsUpdate.wsf"  


Now when you run these steps in your OSD task sequence, the client machine will identify which site it is on and then install any required updates from the local WSUS server.

Labels: , , ,

Get WMI Query v1.3 Released
UPDATE: Get WMI Query v1.5 is now available - click the Downloads button above to obtain

================================================================

We are pleased to announce the release of Get WMI Query v1.3.

This program is designed to help in a SCCM environment where there is a need to provide a multiple set of drivers to a task sequence during an operating system deployment. This may also assist in the same process for those using WDS.

This program can be run on a machine where you require to retrieve the exact model from the WMI under Win32_ComputerSystem. It will then give you the model and also the WMI Query that you would need to add to your SCCM or WDS task sequence.

As an example, below is a step in my task sequence for drivers for a HP Probook 6460b and the WMI query that I use as an option on this step to enable this step to run only on a HP Probook 6460b.



By running the Get WMI Query program and pressing the Get WMI Query button, it will return this information for you and you can simply copy and paste it into your own driver steps.


DOWNLOADS


COMMENTS

If you have any comments or bug reporting for this item, please post them below.

Labels: , , ,

MDT Toolkit speed up during OSD
I was recently given a tip on how to speed up the MDT Toolkit Package part when running the Operating System Deployments within my SCCM environment.

This is a simple yet effective change that slightly speeds things up if you have MDT integration enabled. The change is turning off a built in setting to delay the MDT toolkit from loading for 30 seconds. To do this, follow the below instructions:

Go into your MDT toolkit package source folder and in the Scripts folder locate the ZTISCCM.wsf file.


Then, using a tool like Notepad++ look for a line of code as per below:

 wscript.sleep 30000  

You should then delete that line or just comment it out of the code, then update your required distribution points and give it a try. It will knock out 30 seconds of delay for each part that you load your MDT Toolkit during OSD.


Labels: , ,

PXE Boot problems during SCCM OSD
I recently have had some issues with machines not PXE booting for me to be able to deploy an image to new machines. I couldn't quite figure it out as all of our worldwide sites were working perfectly and the office I was working at was also working in one part of the building but not the other.

I spoke to our networking guys and it turned out that the part of the building I was having an issue with was actually on a different DHCP range so the machines in that part of the building could not see the WDS server correctly and in turn, not PXE boot.

To fix this issue was fairly simple, I edited the DHCP settings for this part of the building and added the following settings:
Having made this change, the machines now PXE boot without any problems.

Labels: , ,

Install System Center Endpoint Protection (SCEP) During SCCM OSD Task Sequence Process
As stated in my previous post, I have been asked recently about installing Endpoint Protection (SCEP) during the SCCM OSD process. This is pretty easy to do and the knock on affect is that you also can have SCEP available to install from your Software Catalog.

To prepare the SCEP software for deployment in your OSD task sequence and also for making SCEP available in your Software Catalog, please see the instructions in my previous post below:

Install Endpoint Protection (SCEP) using the SCCM Software Catalog

Once you have completed this task and confirmed that it is working by installing to a test machine from your Software Catalog, you are now ready to add this installation step to your OSD task sequence.

To do this, you need to add an "Install Application" step towards the end of your task sequence and after the Configuration Manager client has been installed.

Once you have added the "Install Application" step, you need to give your step an appropriate name as below and then click the yellow star to add the SCEP application.


Then select the System Center Endpoint Protection from your own list of applications:


You should then have a step like below:


Now when your task sequence gets to this step, it will install the System Center Endpoint Protection with the default policy applied.

If you have any questions about this guide, please feel free to leave a comment and I'll assist when I can.

Labels: , ,

Email Notification at the end of a SCCM OSD Task Sequence
I have been working on a method to send our helpdesk an email notification when an OSD task sequence has completed.

I started by looking into using the Status Filters and Powershell but this didn't seem to work well enough for what I wanted to do, which was to create a fancy looking email by using HTML for the outputed email.

So, I decided that as I have MDT integrated into my SCCM environment, I could use the Execute Runbook step and design a solution in Orchestrator.

To do this, I created a new runbook in Orchestrator with two very simple steps, Initialize Data and Send Email and then link them together...

In the Initialize Data part, I added the OSDComputerName variable so that I could use that information in my email to be sent....


I'm not going to share my email settings as these are very personalised to almost every different setup so you can setup your own settings under the Send Email options, but remember that you can use HTML to design our email and you can use the Published Data to input the OSDComputerName of the machine that is being built by the task sequence where you will execute this runbook.

Once you have your runbook setup and you have checked it in, you can now edit your SCCM OSD task sequence. You should add your Execute Runbook right at the end of your task sequence (remember to add the Use MDT Toolkit Package step before you run the Execute Runbook step)...


As you can see from above, after you have added your Use MDT Toolkit Package, you should then add the Execute Runbook step (you can then rename it something more appropriate like I have above) and enter the settings like below:


As you can see, I've blocked out my Orchestrator Server but you obviously enter your own server name here. You can then browse to your runbook which will then give you the option to specify the OSDComputerName variable which should be entered as:

 %_SMSTSMachineName%  

You can then save your task sequence and when you run the process, at the end it should send the email you created under the Send Email option in Orchestrator.

If you have any questions about this process, leave a comment and I'll get back to you when I can.

Labels: , , ,