If you haven't already, try using the sample templates in here as your starting point. Provisioning is powrful but almost impossible to work out what is necessary unless you have a starting point.
The template isn't completely up to date with SP1 features, but you should be able to identify the sections that will need changing.
MarXtar Ltd/MarXtar Corporation
LANDesk Expert Solution Provider
The One-Stop Shop for LANDesk Enhancements
Update - New Stand-Alone State Notifier Console for Service Desk Operators
Update - State Notifier now detects machine and user Idle states
Update - WoW & State Notifier now integrate for even more functionality
That is the one I based mine off of. I was informed that I should not map the image share or the image tool location since they are on the preferred server though. Other than that I had used that exact template for the process. (The non HII version)
I'm testing the same templates and I ran into the same problem. Add the action of Partition and set the action type to Mount partition. Then set Disk = 0, Partition id = 2, and Logical disk = D (without a semicolon). Set this up before the Inject script action.
Please use diskpart to list the volume:
in the command window:
sel disk 0
to check if c or d drive exist, if c drive exist, you can inject the unattend.xml successfully.
Have a read of this discussion. I think you will find Luce is right and you need to mount your partition with the new version of WinPE assuming you are on v9.5 Sp1.
Thanks very much everybody, I will try to the steps recommended this afternoon. I really appreciate the assistance.
Ok, looks like the xml is now located in c:\ So it is indeed copying. However, the generic unattended setup process just hangs and the xml doesn't appear to run after the machine reboots. I'm going to try and put it in c:\windows\system32\sysprep\panther and see if that resolves it.
What location should it be going? I had thought previously it was in the root of c:\
Ok, so placing the unattend.exe at the root of c:
Here is what is happening now. I get to the windows login.
(automatic login does not work, my admin user account mpcore does not login on it's own, but can be manually logged in)
After manual login
Shows the Windows background (hangs indefinitely, will not load anything else automatically beyond this point)
Two notable processes in Task Manager are:
As I said, it simply hangs there and does not proceed any further.
You should not get prompted for a login at the first reboot if the image was syspreped properly. If there was an issue with how sysprep was run then this would cause the problem you are having.
I would redo your base image and sysprep again to test.
If your image is a 64 bit version of Windows please make sure to change the unattend.xml file that came with the template if that is the one you are using. The file is setup for the 32 bit version of Windows. This would cause the machine to not autologin. The first time I tried them I had this problem, I over looked the note in red on that page.
I do not believe it's an issue with the xml file or the sysprep image. We are using these same copies in our OSD scripts with no issue. We have our own xml file, I am not using the template version. The image file we are using is also 64-bit but autologon works with no issue through our OSD scripted imaging.
Looks like going in and updating any of the x86 references to amd64 in the unattend.xml resolved the issue.
Very odd why that same xml works in OSD deployments but not in the Provisioning Deployment.