Forum Discussion
ronald1984
Nov 21, 2022Copper Contributor
SharePoint communication site launch scheduler not working on Root site collection?
Dear all,
Recently during a intranet project we tried to lanch an intranet using the SharePoint site launch scheduler. This did not work wel. In stead of launching the intranet in the intended waves it was launched all at ones. Now is the intranet build using the root site collection. Does the site launch scheduler not support launching the root site collection?
We also tried to use site site launch scheduler on other site collections and this seems to work just fine.
Anyone got any ideas?
Kind Regards,
Ronald Laan
I have spoken to one of my connections within Microsoft about this and it turns out I misinterpreted the following note:
Launches must be scheduled at least seven days in advance and each wave can last one to seven days.
https://learn.microsoft.com/en-us/microsoft-365/enterprise/portallaunchscheduler?view=o365-worldwide
This quote actually means that waves have to be scheduled at least seven days in advance. At the launch date of the first wave the launch process will start indexing all the added security groups / users. After indexing the launch process will make the portal available to the the indexed users one by one. Therefore this process can take up to seven days.
The exception which can be set for example for testing purposes will also follow this process and is in essence also a wave.
- ronald1984Copper Contributor
I have spoken to one of my connections within Microsoft about this and it turns out I misinterpreted the following note:
Launches must be scheduled at least seven days in advance and each wave can last one to seven days.
https://learn.microsoft.com/en-us/microsoft-365/enterprise/portallaunchscheduler?view=o365-worldwide
This quote actually means that waves have to be scheduled at least seven days in advance. At the launch date of the first wave the launch process will start indexing all the added security groups / users. After indexing the launch process will make the portal available to the the indexed users one by one. Therefore this process can take up to seven days.
The exception which can be set for example for testing purposes will also follow this process and is in essence also a wave.