WIE/WinPE Incorrect Login
-
having same issue, what was the full fix for the issue
-
@kdancause @QW Sorry for the late response guys. You need to go into the web console under admin settings -> security and get your "global imaging token." If you don't have one, you can hit the action menu up top and generate one. Once you have that, you can either edit the batch file that creates the WinPE media to include that (set UniversalToken=), or if you have already generated one, you can mount the WIM with dism and edit the uToken.txt file that is in \Windows\System32 to include the universal token you grabbed earlier.
This was the only way I could get past the login screen on several devices, including Surface Laptops and Lenovo Laptops. Hope this helps.
-
@edwinjamess Thank you, tested it and everything is working now.
-
Hello. I know this is an old post but I am having the same issue. I saw the "fix" but it wasn't clear to me. Can you please clarify the global token thing?
Thx
-
@dhdag22 No worries. Which part specifically? It's been a while but I read through my comment above and that is what I remember doing. Do you need help generating the token? Or adding it to the pre-boot WIM?
-
@edwinjamess appreciate the quick response. We still use Clonedeply at my workplace. Haven't upgraded to Theopenem as of yet. We image from a USB boot drive. I already have a WinPE boot drive created. But I'm getting the login error when I try to image our new HP model. I don't see an option to create a token in Clonedeply under security. Also, where is the wim file be located? I'm kinda new to dealing with those files. We've been imaging with the Linux based boot drive. It's been pretty straight forward.
Thx
-
I'm guessing you are moving to WinPE because you are having issues with the LIE. The better option is probably to move to Theopenem
-
@theopenem_admin @DHDAG22 Agreed. The migration wasn't too difficult either and might be even easier now than it was a year ago.
To answer your question though, it's called "universal token" under security in clonedeploy. We PXE boot everything but I assume that the WinPE USB is just an extracted WIM, so you'd copy that universal token from your server add that to the file under \Windows\System32\uToken.txt.
But I do suggest that you upgrade. I only use Theopenem for imaging and I still think it was worth the upgrade.
-
@theopenem_admin LIE? Is this in reference to Linux?
-
yes it is
-
@theopenem_admin then yes. That is why. Can theopenem be installed on the same box until the setup is done?
-
@theopenem_admin also, can theopenem update be installed on top of clonedeploy or do I have to install the full version?
-
The automated installer won't work correctly if CloneDeploy is installed. It should be a clean Windows install.
-
@theopenem_admin Ok. Can the images from clonedeploy be copied over? I have about 12 of them. I can see them in a directory.
-
@theopenem_admin ok so I upgraded to theopenem. Got the token. I'm stuck after that point. Can you provide any info?
-
You just need to put the token in the wie_build script like the com server url and build it.
-
@edwinjamess This fixed my problem instantly thanks for posting this fix !!!