Office 365 News – First release for select users


 Office365logo

First release can now be offered to a select group of users!

(Including a funny mistake by a Microsoft developer)

ImageLife made even simpler for the admins

First release has until now been something that you do not want to enable in a production tenant for the organization, because the impact can be to big with untested changes and additions made regularly.
The common option for the administrator thirsting for knowledge has been to create an evaluation tenant and enable First Release there.
Cumbersome and difficult…is what that was!
A drawback has also been that you could not test anything with the real users, real data or real life scenarios.

No more so, now, the option to enable First Release for only selected users are available.

This is how you do it:

1. Log into your tenants Admin portal: https://portal.office.com/admin/default.aspx
2. Go to Service Settings, Updates.
3. Under First Release, check Select People, you will get a popup asking if you are sure, click Yes.
4. Locate the users you want to set as first release users.
5. Select the users in the box below and click on save (It does not have to be administrators).
5.5 Bulk update (You can also create a list of UPN’s and sumbit it as a bulk update.)
6. Done!
7. Undo

In Pictures:

1. Log into your tenants Admin portal: https://portal.office.com/admin/default.aspx

FirstRelease1

2. Go to Service Settings, Updates.

FirstRelease2

3. Under First Release, check Select People, you will get a popup asking if you are sure, click Yes.
(Entire organization is the old choice, this affects everyone in the tenant)

FirstRelease3x

Like I said, select Yes in the popup dialog.

FirstRelease4
4. In the dialog to your right, search for the user/users you want to set as First Release users.

FirstRelease35x

a. Start typing aname to search for the user…

FirstRelease5

b. Located users are moved to the userslist.

FirstRelease6

c. Select all users in the list.

FirstRelease7

5. Select the users in the box below and click on save (It does not have to be administrators).
(You can also create a list of UPN’s and sumbit it as a bulk update.)

FirstRelease8

You do not get any conformation that it is changed, but it is.

5.5 Bulk update

For a bulk update, do this:

a. Create a list of the users UPN’s, User Principle Names (i.e. Emailaddresses) and save it as a textfile (.txt)
The file can named anything and can be saved anywhere you like.

FirstReleaseBulk3

b. In the Admin portal, Service Settings, Updates, Click on Bulk add people

FirstReleaseBulk0x

c. Browse to your userlist

FirstReleaseBulk1

d. Select the file and click Open

FirstReleaseBulk4

Note the path…(someone at Microsoft made a mistake…\fakepath\ ??). The path shown does not matter, it will work, trust me!

FirstReleaseBulk5x

e. Now click on Next to finish

FirstReleaseBulk6

f. As you can see, the result is shown in the resultlist, success and fail are listed. You can also get a view of a very simple logfile.
Click on finish when you are ready.

FirstReleaseBulk7

Bulk import Done!
6. All Done!

7. Undo

To reset the tenant and go back to noone having first release, do this:

In the Admin portal, Service Settings, Updates, Click on Standard

undo2

Agree to the popup

Undo

And you’re back to normal!

I’

Credits

Niklas Danell, Microsoft Sweden
Erik Fryksén, Xperta AB

References

Microsoft Support on the First Release options

  Office365logo _________________________________________________________

Enjoy!

Regards

Twitter | Technet Profile | LinkedIn

Advertisement

Installing Cumulative updates – current best practice


This is not brand new info, but I think it is important enough to mention again. Huge improvement!

Just a repeat on the current(August 31, 2011) best practice:

Updates for SharePoint 2010 Products
http://technet.microsoft.com/en-us/sharepoint/ff800847

Best practice

The packaging of cumulative updates changed as of August 31, 2011. The following packages are provided for cumulative updates:

  • SharePoint Foundation 2010
  • SharePoint Foundation 2010 + SharePoint Server 2010
  • SharePoint Foundation 2010 + SharePoint Server 2010 + Project Server 2010

As a result of the new packaging, it is no longer necessary to install the SharePoint Foundation cumulative update and then install the SharePoint Server cumulative update.

Previously, the recommendation was to install first foundation, then server, then project if you had project server installed. What this means is that you no longer have to do all of them, just the package that contains all of your updates. If you are running server, install the server package only. (these packages have before been called Überpackages, they are now ‘reinstated’)

Happy patching