Hi All
In a Business scenario, we can setup several VHD
all-in-one box Environments in the same Datacenter for various purpose.
One issue is the standard base URL that usually is https://usnconeboxax1aos.cloud.onebox.dynamics.com/ for all Envs.
In order to change it and allow the team to reach the different Envs, for each Dev Box replace
“usnconeboxax1aos” with the desired URL like “XXXXXXX”:
1- Modify Endpoint URL on IIS
2- Modify web.config files in the C:\AOSService\webroot
and replace all standard “url name” entries with the new one (XXXXX)
3- Modify wif.services.config as per the previous step
4- Again on the VHD VM, modify “Hosts” file on C:\Windows\System32\drivers\etc like that:
127.0.0.1 xxxxx.cloud.onebox.dynamics.com
127.0.0.1 xxxxx.cloud.onebox.dynamics.com
5- Change the “hosts” file on C:\Windows\System32\drivers\etc
in your Laptop, like:XX.XX.XX.XX xxxx.cloud.onebox.dynamics.com
where XX.XX.XX.XX will be the IP of the VHD Box
You have to add an entry for each VHD URL Env.
You have to add an entry for each VHD URL Env.
Till Soon!
8 comments:
Ciao Denis,
edit file hosts of PC of collegue or customer can be difficult, for a customer I created a new DNS zone in Active Directory that is called exactly as url of the VM and inside I created a new record A, without name, with the IP of the VM
Gabriele
Great Gabriele, you are right.
As you know we share our first experience that for sure can be improve.
So again thank you!
Lastly, when you change the standard URL the Workflow and the Task Recorder download doesn't work.
I'm trying to find an workaround and I hope in the next days I came up with another post.
If you find an workaround feel free to share with us!
Greetings!
hi,
I know that it's important share experiance and my post is for improve it :)
I think in the next days I'll must work with workflow issue ...
see you soon.
Gabriele
Hello , thanks for this post but it didn't work with me and the VHD crashed and gave me internal error 500, can you suggest what to do?
usefull article. Thanks for sharing.
MS Power BI Training in Hyderabad
You can expose the D365FO client by creating your own DNS records, an Azure AD app registration and by modifying 3 config files on the AOS server.
Check this tutorial: https://cloudtotal.blog/2019/08/tutorial-expose-a-dynamics-365-for-finance-and-operations-onebox-on-a-custom-public-domain/
when we change the standard URL the Workflow stops working in dynamics 365 finance and operations . cpuld you please suggest.
When we try this, renaming it to example: https://devbox1.cloud.onebox.dynamics.com
On login you get the exception: AADSTS50011: The redirect URI 'https://devbox1.cloud.onebox.dynamics.com/' specified in the request does not match the redirect URIs configured for the application '00000015-0000-0000-c000-000000000000'
Any idea?
Post a Comment