You know that the server is running, but your RDP connection request is denied.
This might be due to the introduction of the IP access check introduced not so long ago and on production environment servers. To get around this you need to add your IP address to the white list for the environment.
To do this click Maintain and Enable access:
Select Enable access:
Click + to add a new rule:
Fill in the form with a relevant name and the IP address to white list:
To get your IP you can ask Google or use one of the many web sites offering that service. For example www.whatsmyip.org:
As soon as your have created the new rule you’re good to go (and connect):
When looking at the hosted environments in LCS sometimes the tiles showing updates doesn’t seem to update probably. The symptoms could be that the numbers indicate that you’re missing some updates after updating it all or that the Last run date isn’t updating.
The status is updated through a scheduled task on the server.
It runs a powershell script in C:\LCSDiagnostics\ called CollectData.ps1
You can run it manually (through an elevated powershell) and that should hopefully update the figures.
It would have been nice to be able to see the run history on the task in the scheduler but for some reason that has been disabled:
That is easily fixed. Open the Task scheduler as Administrator and that gives you the option in the right most part of the form:
In LCS or New Dynamics AX you might have noticed that you have buttons missing their icon/image. It looks like this:
The solution is really simple. Add the sites as trusted sites and you’re good.
Open Internet Options in your browser and go to the Security tab. Select Trusted sites and click Sites:
Add the current site to the list:
You’ll need both LCS and AX on the list to keep them both looking good.
We have been using Lifecycle Services (LCS) for hosting environments for both AX 2012 and AX7 (sorry, New Dynamics AX) so it was somewhat a trivial task deploying new servers. Until we met Azure Resource Manager, that is. Adding servers to an old project ended up giving us this error message:
Lifecycle Services can’t connect to the Azure subscription using Azure Resource Manager. Click the Microsoft Azure Settings button and edit the selected Connector to provide the required permissions to ERP applications in your Azure subscription.
The fix is fairly simple. Go to the Azure connector in your project. You’ll find it in the Project settings. Select it and click Edit. What you need to do is to flip this one to Yes:
It will then lead you through a couple of steps regarding your management certificate and how you need to download it and upload it to the Azure Portal. No need to worry about that because you already did that when you created the connector so just click Next.
You could then end up with another obstacle in the form of missing rights on the Azure tier:
Go to Azure Portal and go to your subscription. Click this button to do add access:
The following is pretty straight forward. Select a role and select the user:
Going back into LCS and click Next might present you with the same error like above with the Dynamics Deployment Service needs access but hang in there. It seems like there’s a bit of delay, so just give it another go after a minute or two.
As soon as your connector has been updated you’re good to go and can deploy the server.