Thanks Kari,
Now I have updated the password for Administrator and also added another local account for user. After rebooting system as mentioned in 7.12, machine only show user I created in answer file and does not let me change anything. Also when entering password I get the following error.
First, the message shown in your screenshot has nothing to do with the password of the account in question, and it is not an error message. It simply tells that you are trying to sign in to a Hyper-V virtual machine using a standard account in enhanced session mode. As enhanced mode is based on remote desktop protocol (RDP), and because RDP only allows authorized users to sign in, sign in fails due lack of authorization.
In Windows 10, local admin accounts (user group Administrators) are automatically granted RDP access. Standard accounts however must be added to Remote Desktop Users group to enable RDP sign in. This applies to normal remote desktop connection to a physical or virtual machine, or in case of Hyper-V, use of RDP-based enhanced session mode.
Short: a user account must belong to either user group Remote Desktop Users or user group Administrators to allow that account to use remote desktop connection or Hyper-V enhanced sesion mode. RDP also requires the account to have a password. RDP requires user account to have a password.
Simple workaround in your case is to add standard users to Remote Desktop Users group in answer file used when running Sysprep. When you create standard user account in tutorial step 4.8, add user not only to group Users, but also to group Remote Desktop Users:
Notice that the separator between groups is a semicolon(;) , and that after the semicolon before another group there is no space.
Correct:
Users;Remote Desktop Users
Not correct:
Users; Remote Desktop Users
Kari
Hi Kari,
First I'd like to join all the compliments provided since you wrote this tutorial. Great work for people you don't even know. Thank you.
I've followed your tutorial to the bit and created a working install image that worked like a charm 100th of times. I also split it and used FAT32 USB stick (using your 'Split Install.wim' tutorial) with no issues. That was when Windows 10 1709 was in place. I now want to update the custom image to version 1809 and install some new apps on my custom image. Do I need to start everything from step one or can I "recycle" the xml files?
Basically I've created an install.wim as explained in Step 6 & 7, split it and replaced the install*.wsm files on my usb stick. However when i run this setup I get 'No images are avaiable'. I tried also the un-split install.wim on a NTFS stick with PC that can read it however I get the same error.
In short:
1. what am I doing wrong?
2. Are there steps I can skip when I want to update my image (upgrade OS & ceate image with different apps)? If it possible to skip steps could you please be kind enough to describe exactly what needs to be done?
Thank you so much,
Harel
Hi guys,
I am new around here with Win10 deployment. I have successfully followed this tutorial Windows 10 Unattended install media Win10.Guru, which is basically the same as this one.
When done, I ended up with 12GB wim file. This consists of three images: one clean install with support apps, one same as before but with specific applications and the third one with another addition of MS office and such. Getimageinfo shows this:
as well as this for every index:
When importing to MDT here is what I get:
I received no errors when capturing images by mounting virtual disks nor when creating ISO. Also, startup procedure goes fine however I have no editions on my image list.
Should I use generic VLK or was it right to use our company VLK? Any ideas?
Thanks for your time guys!
Cheers,
W
I have managed to fix everything.
Now I have another problem. The installed image wouldn't read license key from my BIOS. Is modification of ei.cfg right solution or is there another way to force it?
Thanks for answer!
Best regards,
Waldo
Hi Kari,
I have 4 ISO file I want to create a UEFI USB drive (include those 4 ISO or windows image), I used WinSetupFromUSB_1-8_x64 but for some reason when I create the UEFI USB with that App is working good on new PC or laptop models. On the old ones, it is not showing the UEFI USB but if I use the same flash drive and create a UEFI USB with one image with rufus works fine. do you have any idea what is wrong? or do you have another App that works better for me? create a UEFI Bootable USB with multiple ISOs...
thx.
Ludwin,
I had similar situation as you did. 4 different win10 images. Put them in a single wim and then proceed as instructed in this topic.
Cheers!
I have the most now up and running. Thansk for the kind help!
I have a thing to ask: when you ready to make a new install.wim you said make a scratch and image dir on the root of the C: drive. Is there a way to remove those dirs automatically on startup? F.E. Can i make a batchfile which will be doing the deleting for me? Furthermore i have virtualbox guest additions installed for file transfer. Is there anyway to get the netwerkmapping to be not shown in the new install? And i want to remove the guest additions tools in the new installation before a new user sees it.. Is that possible?
Last question: how do i pin 2 taskicons, f.e chrome and libre office?
//EDIT: I've unmapped the network drives by the hand, does the trick aswell. :)
Waldo, can I ask how you fixed this? This is what I'm getting also and I've gone through all the steps twice now. I'm sure I'm fat fingering something but I can't figure out what.
Quote
