interpreted and created, even when service offering is not subscribed or not
used yet.
Service globaldnsrecords are ignored when onboarding a tenant. Virtual Server
and Server globaldnsrecords are applied when onboarding a user
Service globaldns records are now applied when service is applied/activated
DNS record definitions removed for those services where no globaldnsrecords are
user
TaskManager unhandled exception handled
Server:
Added IPv6 support for all DNS Providers, but only tested ISC BIND & MS DNS
Enterprise Server:
Added support for IPv6. Hyper-V not tested, and probably doesn't work.
When using IPv6 with Hyper-V it assigns "/CIDR" to the subnet mask, and I don't
know if this is the correct implementation.
Portal:
Modified all IP input masks to accept and validate IPv6.
IP Ranges support IP/CIDR format.
A) Powershell support added within the provider
B) Now returns the actual deployed language packs
C) The PeoplePicker points to the organization OU and shows only the users from
the tentant organization. A requirement when used with Exchange 2010 SP2
Addressbook Policies
D) Shared SSL root added to use wild card certificates as part of hosting plan.
When enabled the host name is generated.
E) Search fix: Provisioning of localhost file where the server component is
active. This system expected to be the search server. Within the local hostfile
the sites are listed with their local ip address so the search server can resolve
the site and crawl through their data.
This component needs to be compiled with .NET 2.0 together with Provers.Base,
OS.Windows2003, OS.Windows2008, Server.Utils, and Server components.
Out standing is to update the build and deployment package for a dedicated
deployment packaged so this component is using .NET 2.0, all other should be
using .NET 4.0. This will eliminate the configuration circus that was required
to get the .NET 4.0 version of this component working previously.
