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
-
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. -
-
@coliver said in Surface Pro 3: Boot from USB:
psexec \\SurfaceName -i -s cmd.exeTry something like that.
Same result
-
Okay,.. I see what psexec is suppose to do, and I can do some things. however anything that requires elevated rights fails.
-
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.
-
Restart / Refresh started... Now int the hands of @art_of_shred and @Minion-Queen until it's back online
-
Restart/Refresh didn't work
-
Downloaded a fresh install of Windows 8.1 and of course now the darn think wont boot to USB
no matter what I do. -
@Minion-Queen said in Surface Pro 3: Boot from USB:
Downloaded a fresh install of Windows 8.1 and of course now the darn think wont boot to USB
no matter what I do.bahahaha [self-moderated] ing Microsoft. ..
-
Oh yeah this surface is a piece of CRAP!!
-
@Minion-Queen said in Surface Pro 3: Boot from USB:
Oh yeah this surface is a piece of CRAP!!
THIS Surface? You mean, ANY Surface.
-
This one is worse than the others believe me.
-
has anyone called MS yet? It's an MS product - I would hope you could get some sort of support like calling Dell on Dell equipment.
-
@Dashrender said in Surface Pro 3: Boot from USB:
has anyone called MS yet? It's an MS product - I would hope you could get some sort of support like calling Dell on Dell equipment.
Um.... what? Call MS for Support? That's not something that MS does.
-
@scottalanmiller said in Surface Pro 3: Boot from USB:
@Dashrender said in Surface Pro 3: Boot from USB:
has anyone called MS yet? It's an MS product - I would hope you could get some sort of support like calling Dell on Dell equipment.
Um.... what? Call MS for Support? That's not something that MS does.
This is hardware - I'm assuming it comes with at least a one year warranty. You're going to tell me that the Surface Pro line has worse support than crappy ol' Asus junk?
Granted you might be outside your one year warranty, but there should still be someone to contact.
-
@Dashrender said in Surface Pro 3: Boot from USB:
@scottalanmiller said in Surface Pro 3: Boot from USB:
@Dashrender said in Surface Pro 3: Boot from USB:
has anyone called MS yet? It's an MS product - I would hope you could get some sort of support like calling Dell on Dell equipment.
Um.... what? Call MS for Support? That's not something that MS does.
This is hardware - I'm assuming it comes with at least a one year warranty. You're going to tell me that the Surface Pro line has worse support than crappy ol' Asus junk?
I can't believe that you find that surprising. You expect MS to provide support better than Asus? Asus is high quality stuff, MS is famous for being a "no support that you don't pay extra for" company and their Surface line is famous for being total consumer crap. I'm not saying that MS doesn't offer support, I'm saying that I can't think of any device less likely to get support than an MS one.
-
@Dashrender said in Surface Pro 3: Boot from USB:
This is hardware
I'm unclear of the implication. Isn't the majority of Surface issues in software?
