Moving Microsoft Dynamic CRM 2013 Servers - dynamics-crm

I need to move dynamic CRM servers along with SQL Servers to one data center to another. I have new servers in the second DC and both DC's are accessible in different Subnet. What are my option to move this without much downtime?
We are using Microsoft Dynamic CRM 2013 and SQL Server 2012.

If you are keeping the same hostnames and just changing the IPs - then it should be just a matter of copying the VMs and then changing the IPs. A reboot, and you should be good.
Just check the registry to make sure you are using hostnames and not IP addresses. Check this location: HKLM\Software\Microsoft\MSCRM

Related

What IP adresses does LUIS hit?

I would like to open firewall rules for Microsoft LUIS. I have the port number, but I'm unable to find the IP ranges it uses.
The answer would depend on your app's deployment region, and keep in mind, the IP range could change without notice.
You can find a list of Microsoft Azure datacenter IP ranges here:
This file contains the Compute IP address ranges (including SQL ranges) used by the Microsoft Azure Datacenters.
This file contains the IP address ranges (including Compute, SQL and Storage ranges) used in the Microsoft Azure Datacenters. An updated file is posted weekly which reflects the currently deployed ranges and any upcoming changes to the IP ranges. New ranges appearing in the file will not be used in the datacenters for at least one week. Please download the new xml file every week and perform the necessary changes on your site to correctly identify services running in Azure. Express Route users may note this file used to update the BGP advertisement of Azure space in the first week of each month.
Note: These IP ranges change every week so whitelisting by Azure IP is at your own risk.

cannot connect to VM in azure

this is the first time I am trying to host at Iaas level using microsoft azure. I have created a VM, microsoft server 2012. But I cannot access the VM using the DNS name.
Based on the content of the comments, I see three things that could be wrong
1) Apache is not listening on the external IP of the VM
2) Firewall is not configured to allow for access
3) Since you mentioned DNS, is that the *.cloudapp.net hostname or a custom DNS? If it's the latter, maybe it isn't distributed yet or misconfigured?
Which of these did you check already? Then we can guide you through the remaining ones.

How to access an Orchard multi-tenant site externally on the same network

I've got multi tenancy set up on my Windows 7 machine using Orchard 7.1 and IIS 6.1 which I can access locally no problem.
They relevant sites are all added within the bindings of the applicationhost.config file, as well as the computers' host file and therefore show up as they should by accessing the url.
I have previously had a single tenant set up on my machine that meant I could access on my network, which was done by adding the site to IIS then binding to localhost/my ip address etc.
However the issue I am having is how to access these sites via a mobile device/another computer (on the same network) now that I have set it up for multiple tenants.
Any help appreciated
Liam
You'd need some sort of naming service inside your network, something like Bonjour.
Short of that, I guess you'd have to configure those other machines one by one so their hosts files point to the server.
One final possible possibility may be to simply use DNS. There is no reason why you couldn't use a domain that you control to map several names to local addresses such as that of your server.

Can we bring two ec2 instances under one active directory

I am trying to communicate between two ec2 instances which are having windows server 2008 installed. On one of the server I have installed Active directory and I want to bring another ec2 instance under one active directory.
I'm new to Amazon with active directory.
The problem I am trying to address is Installing dynamics CRM on these two ec2 instances. From my assumption or understanding, CRM requires a CRM web server and SQL server under 1 Active directory.
Any comments with links or suggestions would be very much appreciated.
Active Directory relies on DNS, so it all depends how you setup DNS for your instances.
But in summary if instance A is the domain controller for my.domain.com and instance B wants to join the domain then you have to make sure that instance B can get to instance A by resolving my.domain.com to the right IP address of A.
When you create an Active Directory domain controller, the controller itself automatically becomes a DNS server so the easiest way is just to make the default DNS server for instance B the actual IP address of instance A (you should be able to use the internal Amazon IP address as long as it's pingable)
Hope this helps.

How do I connect up my Amazon EC2 instances without manually modifying config files?

I have a three-tier Windows-based web application bundled into 3 AMIs on Amazon EC2 that I use for load testing.
An ASP.NET web application on IIS
An .NET application server
SQL Server
After I launch them, the config files of each tier needs modifying to update the IP addresses.
At the moment I am doing this manually: I connect to the webserver instance via remote desktop and modify the config file to point to the new IP of the application server instance. Then I do the same with the application server to change the IP in the connection string.
This must be a common requirement and I must be missing something obvious. There must be a better way!
I could use Elastic IP addresses, but these machines are only provisioned for a couple of hours at a time, and I would be charged for the addresses when they were NOT in use (which would be most of the time).
Is there some way of persistently naming the machines? Can I somehow get all the machines on the same network and use machine names instead of IP addresses?
I could write some nifty PowerShell script that would perform the modifications remotely. Is there an example somewhere?
I could use a dynamic IP address service. I'm not sure if this would have any negative effect on performance or availability... Are there any downsides to this approach?
I could install some sort of self-configuring service on each machine (which connects to S3? SNS? SimpleDB?) to publish/retrieve the addresses of the other machines and update the config files automatically. Is there an example somewhere?
What is best practice?
You could use Amazon Virtual Private Cloud (Amazon VPC). You have a private subnet where you can assign an IP address to an instance, but it may require launching an instance from command line to assign IP. VPC is charged the same way as EC2.

Resources