we are about to move TFS from phisical machine to Virtual. The machnie includes both application and Data Tier.
The rollback plan is to turn off the vm and turn on the Phisical machine.
Does anybody had issues with this process? or changes that needed to be done?. the machine will have the same name but diffrent IP.
Did I miss anything?
Migrating from physical machine to virtual went smoothly. I stopped the collection before the migration and started them back after and everything worked the same on all users stations.
Related
As recently as Tuesday I've been able to create virtual machines using Microsoft Hyper-V virtualalization software and thus far I've created 3.
All running Win2K12 server with SQL Server as a lab environment for setting up mirroring and replication (all through a legally obtained license, as part of the MS partner program).
The specs of my work laptop are:
Windows 10 Pro
16 gigs of ram
i7-6700HQ #2.60GHz
NVidia GTX 960M
As of yesterday I was not able to create any new virtual machines, with the following
I find this very strange: I've nog been fumbling with rights and/or permissions on my machine.
My troubleshooting log:
A quick check in the local policies tells me the Administrators still have
local log on rights,
Turning all the existing virtual machines of doesn't help,
Windows Defender and Hitman Pro can't find any abnormalities,
Rebooting doesn't help ;)
"This issue occurs because the NT Virtual Machine\Virtual Machines special identity does not have the Log on as a Service right on the Hyper-V host computer. Usually, the Virtual Machine Management Service (VMMS) replaces this user permission at every Group Policy refresh to ensure it is always present. However, you may notice that Group Policy refresh does not function correctly in certain situations. "
https://support.microsoft.com/en-us/kb/2779204
Solution in CMD:
gpupdate /force
Ok, I know what is basically a Hyper-V is.
Simple, a virtual machine. Well, good for testing application and development usage.
Ok, so far so good for the understanding. and here the main question:
Why do you need to install servers in a Hyper-V on a real server?
Isn't that running a server os on the real machine is somehow better performance than running it in a virtual environment?
for example, database server. Install it in a virtual machine? why not on the real machine?
One example of its use would be to create the perfect developer environment if you want to run many different versions of SQL Server on the same physical box.
SQL Server 2005 isn't compatible with Windows 10 so a virtual server running Windows 2003 is better to house it. Windows 2008 for SQL Server 2008 and so on.
This also gives you the flexibility to allocate resources to different VMs and prioritise RAM to the instance that your currently developing against. Giving you server level options with client tools running on the host OS as intended.
Check out this blog post on setting up such a dev environment.
http://www.purplefrogsystems.com/paul/2016/05/using-hyper-v-and-powershell-to-create-the-perfect-developer-workstation/
I am new to Server and VM things. I recently have the following scenario:
I have 1 physical server that has server 2012 R2 installed on it.
My task is to setup two windows 7 VM environment by hyper-v for testing.
Since there are more than two people accessing the VMs in the future. I know the existing user is kicked when another user login to the VM. Is there any ways to configure this such that both users can access without being kicked? (without violating the terms)
I heard about remote desktop service and did some research on it. However, I do not know if it would fit on this scenario. If it fits, can you explain how it will work?
If none of that work, I am thinking my last plan will be setting up more VMs for the group to use.
Thanks
You will have to first add Hyper-v role in your server from server manager.
Since you are planning to add two virtual machines, you must assign 2 static IPs to each of the VMs.
To run concurrent two RDPs in windows 7, you can install this patch in your VM that has windows 7 OS. Once you have added the patch restart the VM and you will be able to access VM with 2 different user concurrently.
I have developed an application using VB.NET and used microsoft access as the database back end.
Deployment reqiurements : The application is to be deployed on a LAN with 5_15 machines. Any user profile can be accessed from any machine. Any changes to the database entries should be reflected on all machines.
I am confused about how I should achieve this deployment. According to my research :
1.The database should be deployed on one machine . This machine will acts as the database server .
My problem(s) : I am familiar with accessing databases on local machine but how to access a remote database?. How will the connection string look like? Do I need to install ms access on all machines or only on the server machine ? Do I have to deal with concurrency issues (multiple users accessing/modifying same data simultaneously) or is it handled by the database engine?
2.The application can be deployed in 2 ways : i. Storing the executable on a shared network drive on the server.Providing shortcut on desktop of each machine. ii. Storing the executable itself on each machine.
My Problem(s) : How does approach 1 work ? (One instance of an executable running on multiple machines ? :s) In approach 2 , will the changes in database entries be reflected on all machines appropriately? In approach 2, if there are changes to the application , is there any method to update it on all machines ? ( Other than redeploying it on each machine ) Which approach is preferable? Do I need to install the .NET framework all machines? How will i set the connection string to be able to access the database in the network?
Will I have to make any other system changes ( firewall,security,permissions) ? If given a choice to install the operating system on each machine ,which version of windows is preferable for such an application environment ?
This is my first time deploying a multi-user database application on a network.I'll be very grateful for any suggestions/advice,references,etc.
I will try and answer your questions:
Yes you should deploy the database onto a central machine. (Although Access may not the best choice for this sort of thing see: Is MS Access (JET) suitable for multiuser access?)
For connection strings look at this site: http://www.connectionstrings.com/access/
For deployment of your executable you should look at clickonce. This simplifies the install and upgrade of your application significantly. A small learning curve now will reduce your administration headache later.
Hello all I have a backed up about 30 servers using disk2vhd and now I have built my first of many hyper-v severs I did not realize this is all command line I did download CoreConfigurator and that does have some functionality I have been looking for. My question is how do I get the VHD files to run a Vitual Machines? its all command line I tried via vbs to mount the VHD's and I have not been able to any help on this would be great!
Thanks!
If you are using servercore, You maybe can do everything from the command line but I always prefer to have one computer running a Non server core version of windows 2008 to be the management server. You will load up Hyper-V manager on the non server core box and manage your Hyper-V server.
To have no "management" servers or desktops on your network will be a big pain IMO for management.
Using Hyper-V Manager you can quickly load the VHD's as VM's.
So load up Hyper-V Manager on a desktop PC on your localnet, and use its connect option to connect to your servercore. (Make sure your firewall settings are ok on servercore using coreconfig)