I've 8 computers running Windows 8 (the basic edition) and I'm trying to run some application on each of them with a batch script.
I tried:
PsExec.exe -i -d -u USER -p PASSWD \\PCNAME explorer.exe
But it gives me:
PsExec v1.98 - Execute processes remotely
Copyright (C) 2001-2010 Mark Russinovich
Sysinternals - www.sysinternals.com
Couldn't access GATE1:
Access is denied.
It works fine on other PCs with Windows 7 Professional.
Does it works just on Pro edition? If so, is there a way I can run something remotely on Win 8?
I resolved the same PsExec "Access is Denied" error on a Windows 8 Pro 64-bit target machine with the following registry modification on the target machine:
Registry Location: HKEY_LOCAL_MACHINE\Software\Microsoft\Windows\CurrentVersion\Policies\System
Add DWORD LocalAccountTokenFilterPolicy
Set LocalAccountTokenFilterPolicy to 1
(Reboot)
In domain based environment, Microsoft PowerShell Remoting may be an alternative to PsExec.
In workgroup setup, especially among many different versions of Windows it may get bit challenging.
PowerShell remoting requires PowerShell 2.0 on both client and server.
Also, ssh with it's all capabilities (including launching remote commands) works under Windows, even free servers (freesshd) and clients (PuTTY family) are available . Downside is requirement for highly privileged account (usually, in some Administrators group) - at least for initial setup.
The GATE1 part in your log is interesting - PsExec requires so called "admin share" enabled (not sure does it work in Windows 8). I'd bet it's not the system, but a network issue.
Related
I have set an Azure Virtual Machine running Windows Server 2016 and now I need to install WCF RIA Services 1.0 SP2 on it.
Until Windows server 2012 I used to do that via command prompt:
msiexec /j RiaServices.msi SERVER=true
However in 2016 I receive the following message:
"You do not have sufficient privileges to complete the re-advertisement of this product. Re-advertisement requires initiation by a local system account calling the MsiAdvertiseScript API, such as through Group Policy Software Development."
Don't know what does it mean or how to make installation works. Obviously I am running command prompt as Administrator.
Any ideas?
I solved this problem changing the command line to:
msiexec /package RiaServices.msi SERVER=true
Still not sure exactly why, but the installation succeeded.
Is the way to manage windows from linux terminal using only base windows soft? E.g. how can send files from linux or run some script? Install ssh server on windows unfortunately not suitable.
I am using OpenSSH for Windows in order to be able to connect a Linux machine to a Windows machine.
To do that I have installed a SSH server for Windows v5.6p1-2.
I also have declared the allowed users.
From my Linux machine, I connect to the Windows machine with "ssh user#machine" command.
My problem is that once connected, I get only some Windows environment variables but not all system and user defined variables.
Is it possible to get all the Windows environment variables ?
Thanks,
"This is to limit security holes."
Check this out it has a few solutions.
http://cygwin.com/ml/cygwin/2006-11/msg00394.html
Is there a way to execute gacutil in to a particular (remote) machine given the IP address (or the workstation name) of the machine?
The machines in question are on an Active Directory Domain.
The user running the script probably won't have any special rights on either their local or the remote machine.
Some cases, will be administrator in machine.
Operating system is Windows XP , and remote machine Win2008 and Win2003.
Any programming language is fine but ideally scripting:
DOS Batch file (bat, cmd)
VBScript (WSH)
psexec
C# (worst option for me)
Have you tried Remote Gacutil? http://remotegacutil.codeplex.com/
You can always use psexec:
copy %Proj_folder%\SomeDll.dll \\destinationHost\c$\Temp
psexec \\destinationHost gacutil -I c:\temp\SomeDll.dll
What exactly is the difference between using
mstsc
mstsc /admin
mstsc /console
mstsc /admin /console
all answers appreciated - in particular if any of these can effect the user being logged out after inactivity.
A little history on this:
In Windows XP, Windows Server 2003, and earlier versions of the Windows operating system, all services run in the same session as the first user who logs on to the console. This session is called Session 0. Running services and user applications together in Session 0 poses a security risk because services run at elevated privilege and therefore are targets for malicious agents who are looking for a means to elevate their own privilege level. (Source)
As a result, the /console switch has been eliminated - starting from Windows XP Service Pack 3, Windows Vista Service Pack 1 and Windows Server 2008.
However, The /admin option lets you connect to Session 0 on a remote computer that doesn’t have Windows Vista SP1, Windows XP SP3 or Windows Server 2008 or later installed.
Concerning Timeouts: The default time out afaik is 20 min regardless of switch.
Previous to terminal service 6.1 you accessed the "console session" of a remote machine by "mstsc /console". After 6.0(6.1 and later) the flag was changed to using "mstsc /admin"
When you use "mstsc /admin /console" the /console is ignored. Similarly if you specified your host with "mstsc /v:servername /console" the /console would be ignored without giving you any warning.
I believe either one should have the same inactivity timers but I haven't confirmed that anywhere.