To recover from previous versions: search on oab.xml within the address list
server, remove all oab.xml files with a size of 1kb and run
Get-OfflineAddressBook | Update-OfflineAddressBook
Decoupling of userprincipalName and PrimaryEmailAddress
OrganizationUsers updated with image buttons with the ability to go directly
to offering settings
When changing primaryemailaddress, sip address changes accordingly
Mailboxes list view updated with Login (=userprincipalName) with the ability
to go directly to user setting
Lync list view updated with Login (=userprincipalName) with the ability
to go directly to user setting
When changing primary email address, upn is changed as well. UPN is not changes
anymore
When deleting user: leaf object error. Fixed: object delete methods extended
with delete Tree
Lync Global Plans cannot be deleted, fixed
Fixed: Hosted Organizations: user principal name updated when settings primary
email address. User principal name will not change when changing the primary
email address.
SIP address is based on EmailAddress
group name of DAG\MailboxDatabase to turn off the load-balancing and instead
use a fixed database.
The default behaviour of load-balancing mailboxes between all Provsioning-Enabled
mailbox databases of the DAG-Group is still present and functioning.
7. Lync – MeetMeetingMax set to unlimited errors out lots of things
8. Hosted Organization – When creating an organization manually, the Org
Name is taken as the first accepted domain for exchange, if this org name
is not a domain it creates the org incorrectly. This should take normal names
and not take this as a domain name for the accepted list, we have a good use
for non-domain org names
get registered within ExchangeAccounts. Server Component updated to ensure
either netbios domain or "samaccountname" is returned. ES Server Component
updated to ensure it's stored within the database.
permission during PF creation, it crashes with information that \user@domain.com
does not exist. There is unwanted "\" character before user's UPN.
Fix on: You can create new public folder, can see in Public Folder Management
Console that it was created OK, with correct implicit rights (Anonymous = Create
items, Default = None, my.hosted.org = Reviewer). But you are not able to see
this Public Folder in WebsitePanel. Cannot add other accounts because there is
nothing to choose.
Applied fix:
if account contains a '@' no '\' will be applied
GetExchangeAccounts sp modified: LEFT OUTER JOIN instead of INNER JOIN
Exchange 2010 SP2 provisioning separated through a new provider
Exchange 2010 SP2 now compliant with product group guidelines
Support for Database Availability Group
Fixed Distribution List view scope to only tenant
Consumer support (individual mailboxes as hotmail) added
Mailbox configuration moved to mailbox plans concept
CN creation is now based on UPN
sAMAccountName generation revised and decoupled from tenant name
2007 (ACL Based), 2010 (ACL Bases), 2010 SP2 (ABP) supported
Automated Hosted Organization provisioning added to create hosting space
Enterprise Server webservice extended with ImportMethod
Mobile tab fixed
Added more information to users listview
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.
