Surface Pro 3: Boot from USB
-
huh. Well, I guess I'd backup the data and wipe it... you've wasted enough time on it already.
-
@Dashrender said in Surface Pro 3: Boot from USB:
huh. Well, I guess I'd backup the data and wipe it... you've wasted enough time on it already.
that is about what we are trying to do. restore to Factory.
-
@gjacobse said in Surface Pro 3: Boot from USB:
@Dashrender said in Surface Pro 3: Boot from USB:
huh. Well, I guess I'd backup the data and wipe it... you've wasted enough time on it already.
that is about what we are trying to do. restore to Factory.
any luck?
-
No luck so far can't get into the darn thing
-
@Minion-Queen said in Surface Pro 3: Boot from USB:
No luck so far can't get into the darn thing
Stuck at the login screen or a non-admin account?
-
@nadnerB said in Surface Pro 3: Boot from USB:
@Minion-Queen said in Surface Pro 3: Boot from USB:
No luck so far can't get into the darn thing
Stuck at the login screen or a non-admin account?
We can get into a non-admin domain account. But can't get into the Admin domain account.
-
@Minion-Queen said in Surface Pro 3: Boot from USB:
@nadnerB said in Surface Pro 3: Boot from USB:
@Minion-Queen said in Surface Pro 3: Boot from USB:
No luck so far can't get into the darn thing
Stuck at the login screen or a non-admin account?
We can get into a non-admin domain account. But can't get into the Admin domain account.
How does that happen? Is it able to talk to a DC?
-
@nadnerB said in Surface Pro 3: Boot from USB:
@Minion-Queen said in Surface Pro 3: Boot from USB:
@nadnerB said in Surface Pro 3: Boot from USB:
@Minion-Queen said in Surface Pro 3: Boot from USB:
No luck so far can't get into the darn thing
Stuck at the login screen or a non-admin account?
We can get into a non-admin domain account. But can't get into the Admin domain account.
How does that happen? Is it able to talk to a DC?
Yes, it can talk to the DC - but whatever the issue,.. you can't sign on as an Admin. and the GPO pushing out the Admin ID isn't updating either.
-
SFC /scannow
^might fix the Windows 8 crap app crash debacle. -
The UserProfile Service is borked... Can only sign in as the user that had it. And even trying to open the User Accounts in Control Panel fails
-
Can't seem to run CMD as Admin:
-
@gjacobse said in Surface Pro 3: Boot from USB:
The UserProfile Service is borked... Can only sign in as the user that had it. And even trying to open the User Accounts in Control Panel fails
Ooooh I hate the control panel crash issue. Don't remember how I fixed it when I had it arrive on my desk.
Can you open stuff as administrator?
Edit wait just saw your CDM post.
-
Can you psexec to it?
Edit: psexec \\$pc -i -s cmd
-
Do you have a sledgehammer?
-
-
@nadnerB said in Surface Pro 3: Boot from USB:
psexec \$pc -i -s cmd
'psexec' in not recognized as an internal or external command, operable program or batch file
-
@gjacobse said in Surface Pro 3: Boot from USB:
@nadnerB said in Surface Pro 3: Boot from USB:
psexec \$pc -i -s cmd
'psexec' in not recognized as an internal or external command, operable program or batch file
You need to download it. It's not built into the system. https://technet.microsoft.com/en-us/sysinternals/pxexec.aspx
-
can you create a GPO for that specific SP3 that adds the standard domain account that you're using to the local admin group? Then have at some of the other fixes again?
-
@nadnerB said in Surface Pro 3: Boot from USB:
can you create a GPO for that specific SP3 that adds the standard domain account that you're using to the local admin group? Then have at some of the other fixes again?
Sounds like GPOs aren't applying. He stated earlier that they have GPO that does that.
-
@coliver said in Surface Pro 3: Boot from USB:
@gjacobse said in Surface Pro 3: Boot from USB:
@nadnerB said in Surface Pro 3: Boot from USB:
psexec \$pc -i -s cmd
'psexec' in not recognized as an internal or external command, operable program or batch file
You need to download it. It's not built into the system. https://technet.microsoft.com/en-us/sysinternals/pxexec.aspx
Downloaded to the local computer and to another computer on the same physical network
Both run, but don't do anything.
C:\Users\PCname\Downloads\PSTools>psexec \\SurfaceName -i-s cmd cmd PsExec v2.2 - Execute processes remotely Copyright (C) 2001-2016 Mark Russinovich Sysinternals - www.sysinternals.com PsExec executes a program on a remote system, where remotely executed console applications execute interactively. Usage: psexec [\\computer[,computer2[,...] | @file]][-u user [-p psswd][-n s][-r servicename][-h][-l][-s|-e][-x][-i [session]][-c [-f|-v]][-w directory][-d][-<priority>][-a n,n,...] cmd [arguments] -a Separate processors on which the application can run with commas where 1 is the lowest numbered CPU. For example, to run the application on CPU 2 and CPU 4, enter: <deleted for space> You can enclose applications that have spaces in their name with quotation marks e.g. psexec \\marklap "c:\long name app.exe". Input is only passed to the remote system when you press the enter key, and typing Ctrl-C terminates the remote process. If you omit a user name the process will run in the context of your account on the remote system, but will not have access to network resources (because it is impersonating). Specify a valid user name in the Domain\User syntax if the remote process requires access to network resources or to run in a different account. Note that the password and command is encrypted in transit to the remote system. Error codes returned by PsExec are specific to the applications you execute, not PsExec.
