I have 2 machines :
Developer machine(running the VS 2008): connected to network abc.lan & VPN xyz.lan
Remote machine(running the service): connected to VPN xyz.lan
On the developer machine, when I goto Debug->Attach to process->Browse(for Qualifier), only the machines which are on abc.lan are visible BUT NOT the remote machine which is connected only on VPN xyz.lan
Is there a way by which the remote machine could be visible across the domain ?
PS : In general, any guideline to do the same would be helpful.
Thanks
You cannot directly attach the remote machine process to debugger, if connected through VPN or Remote Desktop. Instead you can do the following if you have rights there
Install WinDbg with symbols
Use Reflector with Deblector
Install VS on the same machine, access it through RDP or VPN and debug
You can remote debug across domains, but you'll have to enter either the IP Address or the machine name in manually. There are some restrictions, such as needing to use a Local User account instead of a domain account. This MSDN article specifically details it out:
http://msdn.microsoft.com/en-us/library/9y5b4b4f(v=vs.90).aspx
Related
Hi there I wl like to understand: How to do starting a virtual machine and launch it from my client (windows 10 Home Edition based Laptop) using the DNS and credentials provided ? I got the DNS and user credentials.
If you have the VM created and turned off, then you should go to the Azure portal and turn it on, then use Remote Desktop Protocol from your local machine to connect to that virtual machine.
I am trying to install an MSExchange 2016 in an EC2 instance from scratch without success. By from scratch, I mean I start from a new EC2 instance without any AD yet installed.
I am not very familial with Windows Server. I got a lot of problem during the installation. By digging the web, I fixed a lot of them, but I think there is something I miss to succeed in my installation. Any help would be greatly appreciated
Here is the procedure I followed:
I created an EC2 Windows Server 2012RC2 instance
I created a simple Active Directory in AWS.
I provided the AD DNS to my Windows Server (via Network and Sharing Center, properties of Internet Protocol v4)
I joined the server into that AD (Via Control Panel > System and Security > System, change computer workgroup to the domain defined in my AWS Simple AD)
Restart computer
Log into the server as Administrator, with the AD domain
Download Exchange from here
Set-up the active directory, as in this procedure: https://judeperera.wordpress.com/2015/07/24/step-by-step-guide-for-installing-exchange-server-2016-preview/
The Step 4.1. of that procedure indicates to execute the following code
Setup.exe /PrepareSchema /IAcceptExchangeServerLicenseTerms
When I execute it, I get the following error:
I do not understand what I need to do/fix to continue the installation.
Thanks in advance for your help!
The issue you are encountering is that Simple Directory is not an Active Directory product, it is powered by Samba v4. What you need is to setup a Microsoft Active Directory (Enterprise Edition) or Microsoft AD, which is powered by Windows Server 2012 R2. The Simple AD is powered by Samba v4 and is simply Active Directory compatible but does not support the added schema features which are needed by Exchange Server 2016.
The other option is to back away from hosting your own instance of Exchange server and instead take a look at AWS WorkMail. It is an exchange like service which supports active sync with Outlook 2007+ and all current mobile smart devices such as Android and iOS. I currently use this and it took a lot of the headache out of managing my own mail server as the complexities are offloaded to the AWS environment and all you need to do it add mail accounts and group addresses.
Either option should solve your issue.
I have a virtual machine created from an linux image (and powered on). I want to be able to access its console in VCenter, but right now I am getting this error:
"A secure connection to the host could not be established"
The console is a black screen with nothing on it and no interaction. This happens for any VM in VSphere. Bizarrely I can telnet in to the console port 902, but there doesn't even appear to be any attempt to connect to the console (checking tcp/ip traffic in Task Manager).
SSHing in is not possible because the reason I wanted console access to begin with was to run commands to set up an IP address for this machine.
Some facts: Opening an external console window does nothing (same error). I'm running Windows XP Professional (out of VirtualBox if it matters). My colleague on the exact same setup (same version of XP, same version of VCenter) can connect to the console just fine.
Does this problem happen when you connect directly to the ESX/ESXi ?
if not you have connection problem beetween esx and vcenter.
you can find here a list of common ports :
http://kb.vmware.com/selfservice/microsites/search.do?cmd=displayKC&docType=kc&externalId=1012382&sliceId=1&docTypeID=DT_KB_1_1&dialogID=312218113&stateId=1%200%20312216906#vCenter 4.x
Turns out that when connecting to vcenter I needed to use https instead of http. Boy howdy, do I feel smart now.
My development machine is on the corporate network, and I log on to it using my domain account. I have VMware workstation installed, but my virtual machines are not and cannot be a part of the corporate domain.
The problem is that I would like to use the VMware remote debugging option and debug from Visual Studio on the development machine into one of my virtual machines. One of the requirements of remote debugging is that the same user account has to be valid on both machines.
Is there are way to make my domain account valid on a virtual machine that is not on the domain? Or is there a way to make both machines use an account that is not a part of a domain?
If you are debugging native code (unmanaged) using msvmon.exe on the guest OS you can use No Authentication mode to allow any remote machine to connect and attach a VS debugger. This is insecure, and precautions such as appropriate host machine firewalls should be put in place, but this will function without the guest VM needing to be on the domain.
For moreinformation, see this Microsoft KB article, and this step by step visual guide for the connection procedure. Additionally, if you have any issues setting up msvmon.exe on the guest OS see this MS KB article for setup, and this article for firewall issues.
What is the best way to have a virtual operating system have a static IP address in VMWware. I would like to keep the IP address static since it is a virtual server.
You can configure VMware DHCP server [which runs on host OS] to assign a fix IP address to a VM each time.
According to vmware docs, configuration is stored at the following locations:
Windows XP
C:\Documents and Settings\All Users\Application Data\VMware\vmnetdhcp.conf
Windows Vista or Windows 7
C:\ProgramData\VMware\vmnetdhcp.conf
Linux (host-only)
/etc/vmware/vmnet1/dhcp/dhcp.conf
Linux (NAT)
/etc/vmware/vmnet8/dhcp/dhcp.conf
VMWare Fusion for Mac (host-only)
/Library/Preferences/VMware Fusion/vmnet1/dhcpd.conf
VMWare Fusion for Mac (NAT)
/Library/Preferences/VMware Fusion/vmnet8/dhcpd.conf
Static IP and DNS name by MAC example:
host ubuntu {
hardware ethernet 00:0c:29:c0:2c:58;
fixed-address 192.168.118.3;
}
For more details on this please see this blog post.
Assuming you're not using NAT-based VMWare networking, the answer isn't any different for a virtual (guest) server than for a real one. You can:
Assign a static IP via whatever mechanism the guest operating system supports.
Configure the guest operating system to get its IP address from a DHCP server, and configure the DHCP server to return a static IP address for the VMWare instance's MAC address.
If you want the VM slice / VM machine (guest) to have a static IP, assign it to the VM slice. Then on the VM Server select "Bridged" for the network adapter settings. This tells VMWare to use what ever IP settings you have established on the guest.
This works on my machine
Follow these simple steps. Takes just 5 minutes.
1. Note the MAC of the VM
2. On the host machine open C:\ProgramData\VMware\vmnetdhcp.conf
a. Or C:\Documents and Settings\All Users\Application Data\VMware\vmnetdhcp.conf
b. These 2 files are auto synced or mirrored.
c. Open the editor in Administrator mode. Eg notepad++. Otherwise you will get access denied message
3. Add a new entry at bottom of the configuration file, right before the "# End" marker. MyGuestVM is any unique name. Example below
host sunilW2008Server {
hardware ethernet 00-0C-29-05-2B-A0;
fixed-address 192.168.63.222;
}
3. Shutdown the VM and close the Workstation
4. Re-start the VMWare DHCP and NAT services for changes to take effect (From services.msc)
Notes:
the below folders are at sync automatically.. change at one place and the same will be reflected on the other folder
C:\ProgramData\VMware
C:\Documents and Settings\All Users\Application Data\VMware
A simple workaround, configure the vmware dhcp server to use longer leases.
In the vmware config folder (on windows 7 -- C:\ProgramData\vmware) edit the file
vmnetdhcp.conf and change the values of default-lease-time and max-lease-time to
something bigger say 4 months (4mo*30days*24hours*60min*60sec = 10368000).
Then restart the vmware dhcp server. Then release and renew the lease on the guest.
Now your guest IP is static for next four months.
If you prefer to leave the VM host configuration as default, it is also possible to configure the guest machine to request a fixed address for dhcp. This will work even for the NAT network. In the case of Ubuntu and dhclient, this is achieved by the following block in dhclient.conf:
interface "eth0" {
send dhcp-requested-address 192.168.1.222;
}
Source: https://serverfault.com/a/381137