Surface Pro 3: Boot from USB

[nadnerB]

@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?

[gjacobse]

@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.

[nadnerB]

SFC /scannow
^might fix the Windows 8 crap app crash debacle.

[gjacobse]

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

[gjacobse]

Can't seem to run CMD as Admin:

[nadnerB]

@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.

[nadnerB]

Can you psexec to it?

Edit: psexec \\$pc -i -s cmd

[Jason]

Do you have a sledgehammer?

[gjacobse]

@Jason said in Surface Pro 3: Boot from USB:

Do you have a sledgehammer?

Upvoted +1.0E999

[gjacobse]

@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

[coliver]

@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

[nadnerB]

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?

[coliver]

@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.

[gjacobse]

@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.

[coliver]

@gjacobse

psexec \\SurfaceName -i -s cmd.exe

Try something like that.

[gjacobse]

@coliver said in Surface Pro 3: Boot from USB:

@gjacobse

psexec \\SurfaceName -i -s cmd.exe

Try something like that.

Same result

[gjacobse]

Okay,.. I see what psexec is suppose to do, and I can do some things. however anything that requires elevated rights fails.

[gjacobse]

So for giggles I decided to look in the c:\users\ folder to see what was there. Just so happens there are a number of users on this system. Including our NTG account. And two _UserName% where I tried to fix the profile issues.

Renamed the _NTG$ account and signed in,... albeit with a temp profile, but this gives me more access.

Back up and off to PC Settings to kick this puppy.

[gjacobse]

Restart / Refresh started... Now int the hands of @art_of_shred and @Minion-Queen until it's back online

[Minion Queen]

Restart/Refresh didn't work