Much of these are known issues which will be addressed in version 1.5 of the toolkit.
[PowerShell MVP|https://mvp.support.microsoft.com/profile=5547F213-A069-45F8-B5D1-17E5BD3F362F], VI Toolkit forum moderator
Author of the upcoming book: Managing VMware Infrastructure with PowerShell
Co-Host, PowerScripting Podcast (http://powerscripting.net)
Need general, non-VMware-related PowerShell Help? Try the forums at PowerShellCommunity.org
For me it is normal when you are trying to set a new domain for the spec to be asked for credentials. This cmdlet is designed that way and this particular behavior will not be changed for the updcomming 1.5 release. However the second problem is a real one. I've tried to reproduce it with the latest builds and the problem seems to be fixed. So wait for the 1.5 to be released
Good to hear. I searched the communities and didn't see it mentioned so I thought I would throw in my two cents.