I'm trying to setup environment for kernel debugging and use KMDFDrv sample. Host - win 7 x64 wdk 8.1 vs2013RC, target - win8.1 x64 clean installation (no VM).
Both machines in the same workgroup, both firewalls down, UAC on target down.
User and Admin accounts use same passwords. On target WDKRemoteUsers is also created.
When I'm logged on host as Administrator - no issues. When I'm logged on host under user account I see that in "debugger immediate window" everything stops after reporting "Pass" status for actions that been just made - "driver removal x64", "driver preparation", "driver install", "Driver post install". Code compiled correctly for x64, win 8.1.
I'm not getting kd input window, only "debugging is running" msg.
Attaching to kernel on target also fails under user account. kd doesn't appear.
Initially target machine was provisioned and setup from host using user account. Then under Admin account in VS on host I also added target machine without provisioning.
Is there anything I'm missing? Can I do kernel debugging on target when logged on host under user account?
Related
How can I get the password for the Remote User Credentials in TwinCAT XAE.
Context:
I have TwinCAT XAE in development PC-Windows and I have TwinCAT XAR on another PC-WINDOWS which is my Runtime PC. I want to connect both these PCs via Ethernet/IP to shift my code from development PC to my Runtime PC.
I have done the TCP and UDP settings for the runtime PC already.
The Development PC is detecting the run time PC in the select target/System window. But, I am un able to connect them because I don't know the password of the remote user for the remote user credentials window. I have tried the password of the runtime PC (which a PC asks when it starts) and also the default value 1, as mentioned in some of the online videosenter image description here
You need to enter the credentials for an administrator account on the PC. The default username/password of "Administrator/1" only applies to factory default Beckhoff PLCs, and not your Windows PC that you have created yourself. To solve this issue, simply create an account called "Administrator" on the Windows 10 PC running the XAR and set a password of 1.
I have a Windows Server 2012 R2 instance running in VirtualBox. Within this VM I have two users, Admin and vagrant where vagrant is non-administrative.
When interacting into the VM via VirtualBox, I am having no issue connecting into either Administrator or vagrant. But when I use Microsoft Remote Desktop, I can only login to the Administrator. As I attempt to login as vagrant, I keep getting the following
The requested session access is denied
According to this potential solution, I have to "Remove the /admin parameter in the remote desktop connection". I have no clue on how to go about that.
Any feedback on this is much appreciated, Thanks!
Try opening the remote desktop application "fresh". Make sure you are not using a saved shortcut to login with the admin account.
Make sure vagrant is a member of the windows "remote desktop users" user group. Under user accounts on the target VM.
On a Surface Pro 3 with Win8.1, already have VirtualBox 5.0.6 installed (works fine with Linux images), just installed Genymotion 2.5.4.
Every time I try to start Genymotion, it asks for admin privileges to invoke something on VirtualBox. Why does this need admin? Any way to avoid this?
According to Unable to create Genymotion Virtual Device a number of people think it shouldn't and I can't find any reference on Genymotion's website that they need admin.
The admin privilege appears when Genymotion creates or configure network interfaces though VirtualBox. This network configuration is unfortunately mandatory for the software to work correctly.
The last changes on Windows and VBox obliges us to do it more frequently so that's the reason why you see it each time you start the program.
I encountered this problem with my non privileged user accounts using Windows 10. When Genymotion runs for the first time as the current user, it will create a virtual interface if it does not see one defined in the users profile. If your account has Administrator privileges, it will create the interface without issue. As a non privileged user, you will get prompted for admin credentials so that a new virtual interface can be created and defined.
My workaround was to run Genymotion with an account that has administrator privileges so that the virtual interface is defined and the Genymotion interface starts up. After that, I preserve the following directories in:
C:\Users\%USERNAME%.VirtualBox and
C:\Users\%USERNAME%\AppData\Local\VirtualStore
When I have a new user that needs to run Genymotion, I have them run a script that restores these directories to their profile. They can then run Genymotion without needing Admin credentials.
From a Windows7 host, I have a process running under a Windows10 VM from VMWare. Using Visual Studio 2013 and the VMWare remote debugging plugin, I want to attach to this process. When I try, I'm prompted for my Username and Password but after entering such, I get the error:
Login Failed. Authentication failure or insufficient permissions in
guest operating system.
The "Attach to Process" dialog has the correct "Running Virtual Machine" and associated "Virtual Machine Location". The "Remote Debug Monitor" is set to the path on the host of ...\Remote Debugger\x86\msvsmon.exe. The "Remote Debug Monitor Name" is set to "VMDebug".
My Win7 host is part of a domain but the Win10 guest is not. They have different passwords. I am able to do remote-debugging on a Win7 VM that is also on the domain. There I connect as "COMPANY\bcwhite" with my password that is the same as the host.
The first obvious question is: What is the correct "User name" because Win10 doesn't make this obvious? Is it "Brian White", "bcwhite", or "bcwhite#example.com"? Granted, I've tried all three and always get the same error.
The second question is: What other permissions could the guest operating system need? How do I get more information?
Trying to configure Visual Studio 2013 (pro, FWIW) to debug a VirtualBox host. I followed this guide and set up the host correctly: It works for kernel mode, but not for user mode. Here is the debugger settings:
When I use kernel mode it works (and I'm debugging the kernel successfully):
But I cannot do it for user mode. I ran:
dbgsrv.exe -t tcp:port=53902
and saw that dbgsrv.exe actually runs, but still I get this:
Actually it makes sense, since I never specified the machine name/IP (where should I enter it?).
The firewall is off and the machine is accessible via network (files sharing).
So how to accomplish user-mode-debugging (Windows User Mode Debugger, not Remote)?
Ok, silly me... the "Computer name" must match the VirtualBox host name...