Deprecated: YoastSEO_Vendor\Symfony\Component\DependencyInjection\Container::__construct(): Implicitly marking parameter $parameterBag as nullable is deprecated, the explicit nullable type must be used instead in /home/nubelus/sharedove/adisjugo/wp-content/plugins/wordpress-seo/vendor_prefixed/symfony/dependency-injection/Container.php on line 60

Deprecated: YoastSEO_Vendor\League\OAuth2\Client\Provider\AbstractProvider::authorize(): Implicitly marking parameter $redirectHandler as nullable is deprecated, the explicit nullable type must be used instead in /home/nubelus/sharedove/adisjugo/wp-content/plugins/wordpress-seo/vendor_prefixed/league/oauth2-client/src/Provider/AbstractProvider.php on line 416

Deprecated: YoastSEO_Vendor\GuzzleHttp\Client::getConfig(): Implicitly marking parameter $option as nullable is deprecated, the explicit nullable type must be used instead in /home/nubelus/sharedove/adisjugo/wp-content/plugins/wordpress-seo/vendor_prefixed/guzzlehttp/guzzle/src/Client.php on line 181

Deprecated: YoastSEO_Vendor\GuzzleHttp\ClientInterface::getConfig(): Implicitly marking parameter $option as nullable is deprecated, the explicit nullable type must be used instead in /home/nubelus/sharedove/adisjugo/wp-content/plugins/wordpress-seo/vendor_prefixed/guzzlehttp/guzzle/src/ClientInterface.php on line 77
{"id":1245,"date":"2012-08-22T00:17:19","date_gmt":"2012-08-21T22:17:19","guid":{"rendered":"https:\/\/blog.sharedove.com\/adisjugo\/?p=1245"},"modified":"2012-08-22T00:17:19","modified_gmt":"2012-08-21T22:17:19","slug":"how-did-i-move-my-mothers-email-and-my-wifes-web-site-to-office365-and-didnt-get-killed-in-the-process-part-4-my-wifes-web-site","status":"publish","type":"post","link":"https:\/\/blog.sharedove.com\/adisjugo\/index.php\/2012\/08\/22\/how-did-i-move-my-mothers-email-and-my-wifes-web-site-to-office365-and-didnt-get-killed-in-the-process-part-4-my-wifes-web-site\/","title":{"rendered":"How did I move my mother\u2019s email and my wife\u2019s web site to Office365, and didn\u2019t get killed in the process \/\/ Part 4: My wife’s web site"},"content":{"rendered":"

In the first three posts of this mini series, I was writing about my motives for moving from Linux\/cPanel\/IMAP stack to Office 365<\/a>, about planning and domain verification<\/a>, and about migrating the mailboxes<\/a>. <\/p>\n

In this post I will shortly touch the mailbox migration again \u2013 I\u2019ll talk about setting up the mail redirection, and then I\u2019ll get to the main topic for today \u2013 creating a public web site on Office365, and assigning it a custom domain name, which was previously hosted on the Linux server with cPanel admin interface.<\/p>\n

Setting up mail redirection in Exchange Online – Office 365<\/h1>\n
Mail redirections are common thing with email. You might want your emails being delivered somewhere else beside the main mailbox, either for backup purposes (my motivation), or for any other possible reason.<\/p>\n
Unfortunately, this is not that straightforward thing in Office 365 to do (comparing with cPanel admin software, for example), but it is not that difficult, either. It includes some PowerShelling, though.<\/p>\n
Open the PowerShell console (as an Administrator, if possible), and then type the command:<\/p>\n
$LiveCred = Get-Credential<\/font><\/p>\n
You will get standard Windows credentials prompt, where you have to enter your Office365 administrative credentials<\/strong>.<\/p>\n
$\"redirect1\"$ <\/a><\/p>\n
After you have entered your credentials, execute following commands:<\/p>\n
$Session = New-PSSession -ConfigurationName Microsoft.Exchange -ConnectionUri https:\/\/ps.outlook.com\/powershell\/ -Credential $LiveCred -Authentication Basic \u2013AllowRedirection<\/font><\/p>\n
You will get the following confirmation:<\/p>\n
$\"redirect2\"$ <\/a><\/p>\n
After that, execute:<\/p>\n
Import-PSSession $Session<\/font><\/p>\n
You should get the following confirmation:<\/p>\n
$\"redirect3\"$ <\/a><\/p>\n
\n
If you get an error here, then please execute the following command:<\/p>\n
Set-ExecutionPolicy RemoteSigned<\/font><\/p>\n
And then start all over again. This command loosens the execution policy by allowing the Remote Signed. Note that you need to have admin privileges for this.<\/p>\n<\/blockquote>\n
After this has been done, it\u2019s time to set the actual redirection. Type the following command:<\/p>\n
Set-Mailbox -Identity YOURUSERNAME -DeliverToMailboxAndForward $true -ForwardingSMTPAddress EMAIL@TOFORWARD.COM<\/font> <\/p>\n
Of course, replace \u201cYOURUSERNAME\u201d with your Office 365 username, and \u201cEMAIL@TOFORWARD.COM\u201d with real address. <\/p>\n
\n
Since I was forwarding my mails to my OUTLOOK.COM account, my redirection command looked like this:<\/p>\n
Set-Mailbox -Identity adis -DeliverToMailboxAndForward $true -ForwardingSMTPAddress adisaccount@outlook.com<\/font><\/p>\n<\/blockquote>\n
On the end, let\u2019s release the session with the following command:<\/p>\n
Remove-PSSession $Session<\/font><\/p>\n
Now you can close your PowerShell.<\/p>\n
Short check if everything works as expected:<\/p>\n
1. Send a mail to the Office 365 account:<\/p>\n
$\"redirect4\"$ <\/a><\/p>\n
2. Check if it has arrived there:<\/p>\n
$\"redirect5\"$ <\/a><\/p>\n
3. And finally check if it has been successfully forwarded.<\/p>\n
$\"redirect6\"$ <\/a><\/p>\n
Now, when this has been done, I wanted to create a new web site for my wife \u2013 promise is promise.<\/p>\n
Hosting public site with SharePoint Online \u2013 Office 365<\/h1>\n
Remember, when I was adding\/verifying domains<\/a> to Office 365, I needed to choose if I will use that domain for Lync and Exchange, or for SharePoint Online. Both would not work. It is one of drawbacks for Office 365, but, as we will see, not a huge one (there is a simple workaround).<\/p>\n
My wife has a subdomain, on our primary domain, where her web site is hosted. Let\u2019s call it \u201cmywifesdomain.progressive.ba\u201d for this purpose. To host her site in SharePoint online with this subdomain, let\u2019s go to the Domains option in Office 365 and add this subdomain:<\/p>\n
$\"030$ <\/a><\/p>\n
Remember, root domain \u201cprogressive.ba\u201d needs to be verified<\/a> with Office 365 prior to this.<\/p>\n
After this has been done, choose that this domain will be used for SharePoint Online. Exchange and Lync are staying unselected here.<\/p>\n
$\"031$ <\/a><\/p>\n
When this is done, click on the \u201cSharePoint Online Administration Center\u201d button, to get to Site Collections management.<\/p>\n
$\"032$ <\/a><\/p>\n
Add a new Public Website site collection here. <\/p>\n
$\"033$ <\/a><\/p>\n
Enter web site name, select previously created subdomain as the site URL, choose the site language and time zone, and set the site collection administrator (myself in this case).<\/p>\n
$\"034$ <\/a><\/p>\n
After you click on OK , SharePoint Online will need some minutes to provision your site.<\/p>\n
In the meantime, switch to your cPanel interface, and click on the \u201cAdvanced DNS Zone Editor\u201d Icon:<\/p>\n
$\"010a-__delete_old_,x\"$ <\/a><\/p>\n
Choose to add a new CNAME record, and enter your subdomain in the Name field (\u201cmywifesdomain.progressive.ba\u201d in my case), 3600 as Time to Live value (1 hour), and, in the CNAME field enter:<\/p>\n
XXXXXXX.sharepoint.com<\/font><\/p>\n
Where \u201cXXXXXXX\u201d is name of your Office 365 subscription, and a host address of your private site collections (intranets). If you are not sure what this is, go to the SharePoint online administration, then Site Collections, and look up the domain of all created private (intranet) site collections. That\u2019s the one.<\/p>\n
$\"035$ <\/a><\/p>\n
Now, when you add this CNAME record, go get some coffee, until DNS records are propagated. After you are back, and after you open that subdomain in Internet Explorer, you should see the magic:<\/p>\n
$\"webssite\"$ <\/a><\/p>\n
Now, you just need to design a site, and to enter the materials. But that\u2019s not a topic for today $\"Smile\"$ <\/p>\n
By the way, if you are asking yourself how to host the \u201croot\u201d domain here, and not the subdomain, as in my example \u2013 nothing stops you to call your subdomain \u201cwww<\/u><\/strong>.yourdomain.net\u201d. Note the \u201cwww\u201d part. And then setup the redirection from your domain to www.yourdomain.net, either through cPanel redirection, or software redirection (JavaScript or server side), or even a CNAME\u2026 your choice $\"Smile\"$ <\/p>\n
\n\t\t\t
\n\t\t\t <\/div><\/div>\n\t\t