I'm trying to remotely access to my computer on LAN with CMD by using PsTools. The remote computer uses Windows 10
I tried a lot of things in this thread. I'm still stuck with "Access Denied".
Does somebody knows if it works on Windows 10 Professional ? If yes, is there something special to do before ?
It does work. Check your windows build version. PsExec (tools too I presume) DOES NOT work on the new version 1903, though there is speculation it has stopped working for build versions from 1809. Though I need to mention I am troubleshooting myself now establishing connection to PsExec service since I upgraded to 1903 and reverted back to 1511 (without having to refresh or reinstall windows)
Related
I just installed Windows 10 onto a Raspberry Pi. It started up fine and I can connect (using PowerShell) from my laptop.
I can connect a keyboard and mouse to the Pi but I can't get a login window. All that I can do is change the timezone and reboot. Is there a way to login directly to the device?
I don't need fancy graphical windows. A command line session (à la Linux or PowerShell) would be fine.
If it isn't possible with the core install, does anyone know if Microsoft, or a third party provider, plans to add this feature?
No there is not a command line presented on the local display. The only way to run commands on Win10 IoT is to use PowerShell as described by Keith in this thread or you can use SSH or Telnet. You can interact with applications run on the device via the local display, keyboard and mouse.
Mark Radbourne [MSFT]
You can use PowerShell remoting from another Windows box to do stuff on Windows 10 IoT Core. I've tested this procedure on Windows 10 PowerShell, works fine. Be sure to follow the step to "Remove-Module PSReadline". I was trying to use setcomputername to rename my RPi2 and the command would fail with a command not found error. Once I removed the PSReadline module, the command started working. Hopefully Jason gets this fixed as PSReadline is just too valuable to remove for long. :-)
I have been trying for a couple days to get Windows Management Framework 3.0 to install on my Windows 7 Enterprise, SP1 desktop machine. The installation seems to go fine, and at the end it requests a reboot as it should. After the reboot, it says installation has failed and rolls everything back out.
In the System Setup Logs it shows the following error:
Package KB2506143 failed to be changed to the Installed state. Status: 0x80070005.
I definitely meet the pre-requisites. I have uninstalled .NET 4.5 and 4.0 and re-installed both, with reboots in between. It always comes back with that same error.
Any ideas?
Make sure you run the installation as Administrator. It's not sufficient to be logged on with an account that has local admin privileges; you need to select Run as administrator from the context menu, or run it from an elevated command prompt. I ran into that error the first time I tried to install Management Framework 3.0 by just double-clicking the downloaded .exe file. It worked when I launched it from an elevated prompt (Run as administrator would have the same effect).
For me the problem was the .Net Framework WoW64 features were missing. More specifically mscoree.dll couldn't be found. Installing the NetFx2-ServerCore-WoW64 & NetFx3-ServerCore-WoW64 features fixed the problem for me.
http://josheinstein.com/blog/2011/09/solved-this-program-cant-start-because-mscoree-dll-is-missing-from-your-computer/
I am trying to run an app I created at work (I sent myself the .exe file) so that I could see how it looks on Windows 7.
My laptop (running 64-bit Windows 7) won't even open it, though. It opens some compatibility wizard to try to rectify whatever the problem is, but that doesn't work either.
Is there anything I need besides the .exe itself, that I should have copied over?
A team member using Windows 7 can run it (by checking it out of Subversion and running it in the VS IDE, anyway), but the display if "off" (The FlowLayoutPanel's controls are experiencing a kind of "wardrobe malfunction"). But I, as mentioned, can't even run it.
What might be the problem/solution?
If you are running the Professional edition of Windows 7 or higher then it will include the option to install the "Windows XP Virtual Machine". You can then run your app as normal under the virtual machine, quckest and easiest way to resolve these sort of issues in Windows 7.
IIS 5.1 shipped with windows xp has 10 connection limit. Singll ASP .NET MVC application can use more connections even if HTTP 1.1 is disabled.
To fix this, Microsoft recommends to use IIS 7 Express in XP.
I tried
iisexpress /path:c:\myapp /port:80 /clr:v2.0
and it works in local computer.
This XP computer has number of users. User can log off antytime.
How to run iisexpress automatically if computer is turned on ? I googled but havent found a way like to run it as XP service ?
How to run IIS Express as a process started via a Windows Service describes how to run it from application. However I'm looking a way to use Windows XP as http server without application. Maybe srvany can help ?
I am running tests successfully on Windows XP but not even got a single successful build while running through Windows 2003.
Any one knows whether it is compatible or not as I read on some site that WatiN is fully tested on XP and not on other Windows editions.
I'd ordinarily post this as a comment on Sam's answer, but I'm trying to make a stack trace searchable, so here goes...
WatiN.Core.Exceptions.IENotFoundException : Could not find an IE window matching constraint: Timeout while waiting to attach to newly created instance of IE.. Search expired after '30' seconds.
at WatiN.Core.IE.CreateIEPartiallyInitializedInNewProcess()
at WatiN.Core.IE.CreateNewIEAndGoToUri(Uri uri, IDialogHandler logonDialogHandler, Boolean createInNewProcess)
at WatiN.Core.IE..ctor(String url, Boolean createInNewProcess)
c:\...\WithVendorSite.cs(42,0): at WithVendorSite.VerifyCanLogIn(TargetSite target)
I developed my test on Windows 7 against WatiN 2.0.10.928 but the test was continually getting stuck with a blank browser with about:blank in the address bar when run on Windows Server 2008 with latest WUs, and Enhanced Security Configuration turned off and running the tests elevated (Run as Administrator).
The problem in my case (thanks Sam) was the absence of Microsoft.mshtml.dll in the bin directory (I had figured out Interop.shdocvw.dll was necessary from error messages I'd encountered on the Windows 7 side).
After adding Microsoft.mshtml.dll, things run happily with ESC turned back [but the test process needs to run elevated].
I run our WatiN integration test suite (hundreds of tests) on Windows 2003 with IE6. Works fine, no special tricks done. What is the exception you are getting? Are you sure mshtml.dll (the COM dll somewhere in the windows directory) is registered correctly on this machine? Do you have the Microsoft.mshtml.dll (interop assembly) and interop.shdocvw.dll in the same directory as WatiN.Core.dll?
Update: Its officially supported, from the faq
Which windows versions are supported?
Windows 2000, Windows XP, Windows 2003
and Windows 2008.
Original post:
I use it on vista all the time. I haven't used it on windows server 2003 though.
Have you tried logging on interactively into the server and trying to run the tests manually? It may be because of the account that your build server is running under or some particular security settings you have setup. Have you checked to see if IE is stopping you from viewing the page due to it not being in the trusted sites list?
I was using Watin 1.3 on Windows XP but the same on Win 7 having problem....
Officially Watin 1.3 works on O.S. Xp and earlier on Win XP
But Watin 2.1 works fine on Win 7 and XP.
Officially Watin 2.1 supports any Microsoft O.S.