RDS profile storage creation error

Question

We are trying to create our RDS profile space on a file server in the same domain and are sharing this file server between a Prod RDS farm and its associated DR farm. The prod farm profile storage works great to \SERVERNAME\UserProfileDisks$\Profile Application Access (Prod). When we try to set up the DR farm to the same share, but different folder at \SERVERNAME\UserProfileDisks$\Profile Application Access (DR), we get the following error in the RDS setup in Server Manager...

Could not create the template VHD. Error Message: Unable to connect to WMI on server SERVERNAME, error No such interface supported

The servers are in the same domain and the share and NTFS permissions are all set to allow the RDS farm computer accounts FC access.

I have not found anything useful in my internet searches on this error.

Answer 1

Hi,
If these server are in same domain and in the same network segment. Also already grant access "Share permissions" R/W to RDSH and RDBroker on the share where you would create the user profile disks. The NTFS rights where configured on the share.
Did you configure quota on the disk? a quota on the effected disk which was less than the default size of the UPD template.
If we couldn’t access it, I would suggest you check network connection and share settings. Such as firewall, DNS or security software.
Hope this helps and please help to accept as Answer if the response is useful.
Best Regards,
Carl

Answer 2

Thanks for the reply. While this second RDS farm is in the same domain, it is on a different network segment than the profile file server. The NTFS and share permissions are all set, though.

Answer 3

Hi,
I'm sorry to see your message when I just came back from vacation.
Thank you for your information.
According to your description and the error code, I consider that you could check if the firewall configuration has something wrong. Also check if the third party security software disable the access.
Unable to connect to WMI on server SERVERNAME. Check Windows Management Instrumentation service is running.
Hope this helps and please help to accept as Answer if the response is useful.
Best Regards,
Carl

Answer 4

My bad for not closing this out. Even though everyone was positive that the firewall rules were implemented correctly, a WireShark capture revealed a missing dynamic RPC port. Once we got that fixed, we were golden