Recently I have been getting issues with performing a hybrid configuration from an on premise Exchange 2010 Server running the latest services packs and meeting all the required pre requisites to perform a Hybrid configuration to Office 365.
One of the first steps is to connect your on Premise exchange server to Office 365 using remote PowerShell, following the how to guide it tells you to connect to the following URI in the command below:
When you run this command you will get the following error:
ps.outlook.com] The WinRM service cannot process the request because the request needs to be sent to a different machine. Use the redirect information to send the request to a new machine. Redirect location reported: https://ps.outlook.com/PowerShell-LiveID?PSVersion=2.0 . To automatically connect to the redirected URI, verify “MaximumConnectionRedirectionCount” property of session preference variable “PSSessionOption” and use “AllowRedirection” parameter on the cmdlet.+ CategoryInfo : OpenError: (System.Manageme….RemoteRunspace:RemoteRunspace) , PSRemotingTransportRed irectException + FullyQualifiedErrorId : PSSessionOpenFailed
If you’ve ever connected a workstation to Office 365 and then been constantly prompted for your credentials you know how frustrating it can be. Have you ever checked that box in Outlook to “Remember Password” and then screamed in frustration as yet another logon prompt came up?
Below is a collection of sites that can help you troubleshoot issues logging into your Office 365 account.
Coming from Exchange environments: make sure your Autodiscover DNS records (internal and external both) point to the correct place. See also the Troubleshooting Autodiscover video.
Coming from BPOS (and possibly other Exchange systems) follow the instructions at http://support.microsoft.com/kb/2644437 to remove registry entries on clients that stubbornly don’t update their Autodiscover.
If Outlook discovers the wrong (old) Exchange system you have problems. Use “outlook /rpcdiag” to ensure Outlook is connecting to Office 365. You can also control-right-click on your Outlook icon in your system tray and choose the option for “Connection Status.” You should see connections to the cloud-based e-mail servers, not legacy servers. Good steps at http://www.petri.co.il/testing_rpc_over_http_connection.htm.
The ability to invite external users to the Team site is enabled by default, so site owners and site collection administrators can share the Team site or any of its subsites with external users at any time. However, if you are the Office 365 admin, you can choose to disable the feature for all sites so that no future invitations can be sent. When this feature is deactivated, any external user currently invited to sites will no longer be able to access the sites.
Enabling external sharing is not the same thing as enabling anonymous access. When external sharing is enabled, users must be authenticated (by signing in) before they can access internal resources.
Go to Admin > Service Settings > sites and document sharing.
Do one of the following:
Turn on external sharing
Turn off external sharing
When you deactivate external sharing, any external users who had access to the site at the time the feature was deactivated are denied access to the site and no future invitations can be sent. If the feature is reactivated with external user names in the SharePoint permissions groups, then those users will automatically be able to access the site again. To permanently prevent a user from accessing the SharePoint site, you can remove them from the list of external users.
If external sharing is turned off globally, any shared guest links will also stop working. If the feature is later reactivated, these links will resume working. It is also possible to disable individual links that have been shared if you want to permanently revoke access to a specific document.
Remove individual external users
If you need to remove external users so that they no longer have access to sites that have been shared with them, you can do so by removing them from the list of external users in Office 365 Service Settings.
Go to Admin > Service Settings > sites and document sharing.
Click Remove individual external users.
Select the external users you want to remove, and then click Delete (the trash can icon).
A little over two years ago, I purchased my first MAC Book Pro and have not looked back since. Admittedly, the first thing I did was to install Windows as VM on it, but this was a case of having to because of my day job.
I have recently moved to PKF Cooper Parry LTD as a Infrastructure Consultant. One of my first projects is to migrate a small company’s data to O365 SharePoint. I will be delivering SharePoint training to end users next week, but have identified that the directors of the business all run from MACs.
One question to me in a planning meeting was…. Can I access SharePoint from my MAC? The answer is yes, and in some cases feels simpler to access your data than it does on a Windows PC.
Here’s how you connect your Mac with OSX to a SharePoint library — this requires Office for Mac 2011:
From Spotlight look for “Microsoft Document Connection” and open it.
Click on the “Add Location” button in the upper left and choose to “Connect to a SharePoint Site…”
Press the Connect button.
Microsoft Document Connection, which was introduced in Office for Mac 2008 SP2 can connect to both SharePoint sites and OneDrive (not yet OneDrive for business). Multiple file upload is simple with this application – just drag and drop them into the application then everything is done. The application itself can be seen as a very lite version of SharePoint Workspace, although it doesn’t do much beyond upload, read, edit, check in/check out. You cannot delete a file, create a new folder, or edit its metadata properties in this app, and to get the latest update you need to hit Refresh button.
The TechNet document Plan browser support in SharePoint 2013 says that Safari is “Supported”. Unfortunately “Supported” does not mean that you will get full functionality. There are a hand full of features, that still only work with ActiveX (IE8/9 on Windows,Chrome/Firefox on Windows via plugins). These are important features like: presence information, Outlook integration (stssync), multiple file upload, and so on…)
Be sure to disconnect the remote PowerShell session when you’re finished. If you close the Windows PowerShell window without disconnecting the session, you could use up all the remote PowerShell sessions available to you, and you’ll need to wait for the sessions to expire. To disconnect the remote PowerShell session, run the following command.
How do you know this worked?
After Step 3, the Exchange Online cmdlets are imported into your local Windows PowerShell session as tracked by a progress bar. If you don’t receive any errors, you connected successfully. A quick test is to run an Exchange Online cmdlet—for example, Get-Mailbox—and see the results.
If you receive errors, check the following requirements:
A common problem is an incorrect password. Run the three steps again and pay close attention to the user name and password you enter in Step 1.
To help prevent denial-of-service (DoS) attacks, you’re limited to three open remote PowerShell connections to your Exchange Online organization.
Windows PowerShell needs to be configured to run scripts. You only need to configure this setting once on your computer, not every time you connect. To enable Windows PowerShell to run signed scripts, run the following command in an elevated Windows PowerShell window (a Windows PowerShell window you opened by selecting Run as administrator).