Your account has been disabled. Please see your system administrator

Scenario:

A non-domain joined virtual machine (HyperV) that as just been sysprepped.  SCCM Capture has completed, machine has rebooted but you get presented with Username and password field instead of Windows config options. 

You try to log on with local admin account and get the error "Your account has been disabled.  Please see your system administrator".

Assumptions:

• You've been using SCCM to build machines

• You didn't activate the admin account

• You really can't be arsed to go back to the task sequence and make the change then spend 1hr rebuilding the machine

• You have some form of access to WinPE either via PXE (F12) or USB/CD boot image
•  
• Troubleshooting is ENABLED in your BootPE to allow for F8 to envoke a cmd prompt.

Solution:

Now this isn't going to work for everyone but this is a method I've used previously when I've done something dumb like not enabling the local admin account!

Bare in mind this is for when there are NO ACCOUNTS AVAILABLE !  You may have seen this method elsewhere on the net when they then tell you to log in as an administrator....  Really....  When I've just Googled "I've been dumb and forgotten to activate my admin account"...  You're telling me to fix it by logging on as administrator.... REALLY???

Here goes.

• Boot your machine into WinPE via F12 PXE or via removable media boot disk
• Hit F8 and bring up the CMD prompt
• Nav to C:\Windows\System32
• Enter the following commands:
• Ren magnify.exe magnify1.exe
• Ren cmd.exe magnify.exe
• Reboot your machine
• At login click the Ease of Access button at the bottom left of the screen – tick the box that says “Make items on the screen larger (Magnifier)” then click apply and if you’ve done everything correctly a command prompt will appear.
• Enter the following command:
• Net user administrator /active:yes
• This activates the administrator account
• Net user administrator 123
• (This is telling the administrator account to use a password of 123)
• Try logging on!!!
• Don't forget to go and rename magnify.exe to cmd.exe and magnify1.exe to mangnify.exe

Lenovo X1 Carbon PXE Boot Issues

I  was recently given the nice new shiny Lenovo X1 Carbon to play with and deploy our corporate Windows 7 image to it.  To maintain its slim physique it hasn't got a built in Ethernet adaptor and is supplied with a Lenovo USB 2.0 to Ethernet Adapter.  Obviously we now had to track down the driver to inject to our Boot Image.

Initially we used the Lenovo USB 2.0 Ethernet Adapter Driver 5.4.3.0 which PXE booted but then seemed to fail and hang once WinPE loaded up.

I then downloaded the Lenovo X1 Carbon SCCM Driver Pack which came with v5.12.4.0 which also seemed to give me problems.

Eventually I found that it was the manufacturers Vista driver that worked for me.

From the AXIS website you can download the AXIS AX88772B Vista Driver which worked a treat.  With the SSD this was a dream to image and was quite quick in comparison to others.

Hope this helps.

Chris.

PXE Boot pulling the wrong Windows PE wim

 If like me you are working with multiple architectures of Microsoft OS there will be occasions where you would like to push out a 64bit OS - more so in recent years due to the increasing popularity of 64bit platforms.

SCCM is my weapon of choice but I have found that sometimes even if a machine is placed in the 64bit deployment collection with the 64bit deployment task sequnce advertsied; it will still throw out the 32bit PE.

This is if a collection has multiple advertisments it will churn out the latest image to be advertised.  To get around this I found a great article on "Network Steve" that I have included below:

I had the exact same problem;
I wanted to be able to boot x86 or x64 Unknown Computers and image them. I have figured a very simple and erffective work around to this problem of the last advertised task winning...
I edited the query in the Unknown Computers collection to add: and Name LIKE "%x86%"
here's the complete query for the "Unknown Computers" collection
select SMS_R_UNKNOWNSYSTEM.ResourceID,SMS_R_UNKNOWNSYSTEM.ResourceType,SMS_R_UNKNOWNSYSTEM.Name,SMS_R_UNKNOWNSYSTEM.Name,SMS_R_UNKNOWNSYSTEM.Name from SMS_R_UnknownSystem where Decommissioned = "0" and Name LIKE "%x86%"
Then I created a new collection called "Unknown Computers x64" and used the following query:
select SMS_R_UNKNOWNSYSTEM.ResourceID,SMS_R_UNKNOWNSYSTEM.ResourceType,SMS_R_UNKNOWNSYSTEM.Name,SMS_R_UNKNOWNSYSTEM.Name,SMS_R_UNKNOWNSYSTEM.Name from SMS_R_UnknownSystem where Decommissioned = "0" and Name LIKE "%x64%"
Next, Advertise your x86 Task Sequences to the Unknown Computers query and your x64 Task Sequences to the Unknown Computers x64 query.
Now, as long as the computer is not in the SCCM database, when you PXE boot it will get the correct image.
Good LuckDoug

http://www.networksteve.com/enterprise/topic.php/Boot_Image_pulling_wrong_Windows_PE_interface/?TopicId=25850&Posts=4