6,194
I have tried a couple of times to deploy a development environment from LCS to Azure now,
Every time the Active Directory machine ends up in a "Pending" state in LCS. And I can't get remote access to any other machine than the SQL Server.
What am I doing wrong? Are there any special requirements for the Environment Name, DomainName og Vnet name that I enter in LCS?
Bonus question: Does the Active Directory machine need to be ExtraLarge as suggested by LCS?
*This post is locked for comments
It occurred to me today that the LCS project I was deploying from, originally was an R2 test project I had set up. So today I (once again) removed everything from Azure, created a new LCS project an deployed from that. And ta-da everything is deployed correct and I can connect to it as expected.
I don't understand why the LCS project could break the installation entirely without any warnings or errors during the process. But then again, there are som many things I don't understand :-)
After three deployments I'm happy that my MSDN credits for Azure is renewed in a few days, and I look forward to investigate how the environment can be used. And not least, what is costs...
Hello Palle - this is very unusual behavior. SQL Server 2014 should be on the machine, and it should have a secondary drive attached that has a set of Dynamics AX databases that would be ready to run the Initialization Checklist.
As far as the domain name and VNet name, the only restrictions that I can think of would be Azure limitations on special characters, uniqueness, etc. In the current Dev/Test the VNet also cannot currently exist in your subscription. You could also leave them at the default state which would be contoso.com and the VNet would be created based on the Environment name you choose.
If you continue to have issues when you try, we will likely need to open a support case so we can do some more in depth log investigation and troubleshooting.
Kevin
Hi Kevin,
Thank you for your answer. I have now tried to be patient and leave the machines on for an hour before trying to log on, but still with no luck except for the SQL machine.
On the remaining machines I don't even get as far as to be able to enter any credentials. The machines are simply not found on Azure.
I have now been snooping around on the SQL machine also and it seems like SQL Server actually isn't installed. Status of the machine on LCS is "Virtual machine was successfully provisioned in Azure". I don't know if that means it is also configured or not.
I might try a new deployment, before I run of of credit this period. Do you have suggestions for what I should enter for DomainName and VNet name when creating it? Are there any special requirements for these two field, or can I enter whatever I like?
Hello Palle - the AD machine's Pending state is something that we have written up as a work item to fix at some point, but you should still be able to connect to each of the machines using the credentials found on the Cloud Hosted Environments page. However if you are like me and want to try and connect right after you see the VMs are in a started state, it is very likely that you will have to wait several minutes before the VMs are able to accept a remote connection - generally I have seen wait times between 10 and 20 minutes after the VM starts before all the services finish loading and I am able to connect.
One other thing is that I use the contoso\DynamicsInstallUser to connect to any of the AX specific machines, the other accounts don't have remote login rights by default to the Client machine for example.
Just a couple other quick thoughts as well to reinforce the previous posts - you can definitely use a smaller size for the AD box and others if you want. As we evolve our pre-packaged deployments we will be adjusting the starting sizing in a number of ways and also other types of deployments. With respect to having us run through the initialization checklist for you, the initial thinking is that in a dev/test environment you would be importing a model store and possibly data but we know that won't always be the case so other variations might follow there as well.
Kevin
Thanks Dominic,
I'll do my next attempt using the sizes you do. And yes, there is a lot of stuff that we need to do yourselves. But then again, to be fair, it's still in beta.
I do wonder though, why I should use this setup and not just a demo machine where everything is configured and works.
Maybe my connection problem has something to do with a lack of patience :-)
Hi Palle,
I also see the AD machine stuck at pending state, but I can connect to it alright. I can connect to all VM even though only AOS and CLI are in "Complete" state in LCS.
I used different sizes for the machines:
AOS: Standard_A2
CLI: Basic_A2
EP: Standard_A5
SQL: Standard_A5
AD: Standard_A5 (Will change to basic A2 )
P.S. When I startup AX client....it prompts me to do an initialization...would've been nice if MS spares us that part...
Hi Umesh,
Last time around I didn't take any chances, so I deployed it as ExtraLarge with 8 cores and 14 Gb of RAM.
#1
André Arnaud de Cal...
291,391
Super User 2024 Season 2
#2
Martin Dráb
230,445
Most Valuable Professional
#3
nmaenpaa
101,156
Share
Report
All responses (
Answers (
