Exchange 2010–Office 365 Hybrid Setup – Remote Powershell

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:

$session = new-pssession -configurationname microsoft.exchange -connectionuri https//ps.outlook.com/powershell/ -credential $o365cred -authentication basic

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

After speaking with Microsoft I have identified the URI has changed to https://outlook.office365.com/powershell-liveid/

and the Powershell command is slightly different to include the –AllowRedirection as there are multiple servers to connect to.

The command that worked for me was the following:

$Session = New-PSSession -ConfigurationName Microsoft.Exchange -ConnectionUri https://outlook.office365.com/powershell-liveid/ -Credential $UserCredential -Authentication Basic -AllowRedirection

Advertisements

How to move from Blogger to WordPress without Losing Google Rankings

I have been using blogger now to host my IT Blogs site for five years now, and thought it was about time for an upgrade.

I felt like my site was lacking functionality and design and have had a look around and apparently WordPress is the place to be.. I did not want to lose any of my site stats so spent a while looking into how I could move away from Blogger and be able to keep them all intact… This is what you do:

Step 1. Before You Start

To get started with WordPress, the first thing you would need is a good WordPress hosting company and your own domain name. We highly recommend Bluehostbecause they will give you a free domain and 50% off their hosting plan (special for WPBeginner users). Bluehost is also an officially recommended hosting provider of WordPress.

If you want a Bluehost alternative, then take a look at Siteground who also offer the same special offer to WPBeginner users.

Once you have signed up for WordPress hosting and set up your domain name, the next step is to install WordPress on your hosting account. We have a step by step tutorial on how to install WordPress. Once you have installed WordPress, it is time to move your content from Blogger to WordPress.

Step 2. Export Your Blogger Blog

First thing you need to do is export your blogger blog’s content. Simply log into your blogger dashboard and go to Settings » Other page. Under the blog tools, click on the Export Blog link.

Export Blogger blog

This will bring up a popup where you need to click on the Download Blog button.

Download your Blogger blog's export file

Your Blogger blog’s content will be downloaded to your computer in an XML file.

Once the download is complete, it is time to import it into your WordPress site.

Step 3. Import Blogger to WordPress

To start importing your Blogger site into WordPress, you need to go to your WordPress admin and visit Tools » Import. On the Import page, click on Blogger.

Blogger importer under WordPress import tools

This will bring up a popup asking you to install the Blogger to WordPress importer. You need to click on the Insall button.

WordPress will now download and install the Blogger Importer plugin for you. Once it is finished installing, you would need to click on the Activate Plugin and Run Importer link to continue.

Activate and run blogger importer

On the Import Blogger screen, WordPress will ask you to upload the XML file. This is the file that you downloaded in Step 1.

Simply click on the choose file button and upload the XML file you downloaded earlier. Next, click on the Upload file and import button to continue.

Upload Blogger export file to WordPress

Now if you didn’t select one of our recommended hosts or your site is really large, you may get an error that your file size is too large. In this case, you would need toincrease your maximum file upload limit. If your file is small, then you won’t see any errors.

WordPress will now import your blogger posts one by one. When it is finished, you will be asked to assign an author to the imported posts. You can assign your blogger posts to an existing author (you) or create a new author account.

Congratulations! you have successfully imported your Blogger content into WordPress. However, you still need to make sure that you don’t loose any search rankings and that visitors from your old blog easily land to the same content on your new WordPress website.

Step 4. Setting up Permalinks

Permalinks is the term used for URL structure of individual pages. WordPress comes with a feature that allows you to set up SEO friendly URL structure. However, since you are importing content from Blogger, you would want your URL structure to be as close to your Blogger URL structure as possible.

To set permalinks, you need to go to Settings » Permalinks screen and choose Month and Name as your permalink structure.

Choosing a permalink structure for your WordPress site

Thats it, you should now have transferred your Blogger sites to WordPress.

All I then did was change the www record at my domain name hosting to point to my new WordPress site.

 

By malple1977 Posted in Blog

Office 365 Credential Issues

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.

Browser Not Supported RD Web Access / Server 2008 R2 Remote Desktop Services

If your trying to access a Microsoft Remote Desktop Services / RDS website from a Windows 8 machine or a pc with Internet Explorer 10 or 11 then you will see the error below :-

rdserror

Browser Not Supported - This Web browser is not supported by RD Web Access. RD Web Access requires Internet Explorer 6.0 or later. You can download the latest version of Internet Explorer from the Windows Update Web site

This is caused by Microsoft not releasing an update to 2008 to allow it to be accessed in the later browsers. In order to get it to work we can implement a workaround that forces machines with newer browsers to access the site as IE9 compatability view.

First of all this fix ONLY works on RDS Gateway servers with 2008 R2 SP1 installed. If you try it on a server without SP1 it will get rid of the error but you wont see any remote apps.

1) Login to the RDS Gateway server
2) Open Up IIS Management Console.
3) Branch out the sites and then left click on RDweb. On the right hand side double click on HTTP Response Headers.

rdserror2

4) On the right hand pane now right click and select Add…

rdserror3

5) On the box that appears enter :-

Name : X-UA-Compatible
Value : IE=9

rdserror4

Now do a IISRESET on the server and you should be good to go..

UPDATE : If you have any pending windows updates also install these as sometimes it wont work until they are installed.

VMWare Network Performance Checks

If packets are not being dropped and the data receive rate is slow, the host is probably lacking the CPU resources required to handle the load. Check the number of virtual machines assigned to each physical NIC. If necessary, perform load balancing by moving virtual machines to different vSwitches or by adding more NICs to the host. You can also move virtual machines to another host or increase the host CPU or virtual machine CPU.

Resolution

1

Verify that VMware Tools is installed on each virtual machine.

2

If possible, use vmxnet3 NIC drivers, which are available with VMware Tools. They are optimized for high performance.

3

If virtual machines running on the same ESX/ESXi host communicate with each other, connect them to the same vSwitch to avoid the cost of transferring packets over the physical network.

4

Assign each physical NIC to a port group and a vSwitch.

5

Use separate physical NICs to handle the different traffic streams, such as network packets generated by virtual machines, iSCSI protocols, VMotion tasks, and service console activities.

6

Ensure that the physical NIC capacity is large enough to handle the network traffic on that vSwitch. If the capacity is not enough, consider using a high-bandwidth physical NIC (10Gbps) or moving some virtual machines to a vSwitch with a lighter load or to a new vSwitch.

7

If packets are being dropped at the vSwitch port, increase the virtual network driver ring buffers where applicable.

8

Verify that the reported speed and duplex settings for the physical NIC match the hardware expectations and that the hardware is configured to run at its maximum capability. For example, verify that NICs with 1Gbps are not reset to 100Mbps because they are connected to an older switch.

9

Verify that all NICs are running in full duplex mode. Hardware connectivity issues might result in a NIC resetting itself to a lower speed or half duplex mode.

10

Use vNICs that are TSO-capable, and verify that TSO-Jumbo Frames are enabled where possible.

Overview of the different network adapters for your VMWare Guests

  • Vlance: This is an emulated version of the AMD 79C970 PCnet32- LANCE NIC, and it is an older 10 Mbps NIC with drivers available in most 32-bit guest operating systems except Windows Vista and later. A virtual machine configured with this network adapter can use its network immediately.
  • VMXNET: The VMXNET virtual network adapter has no physical counterpart. VMXNET is optimized for performance in a virtual machine. Because operating system vendors do not provide built-in drivers for this card, you must install VMware Tools to have a driver for the VMXNET network adapter available.
  • Flexible: The Flexible network adapter identifies itself as a Vlance adapter when a virtual machine boots, but initializes itself and functions as either a Vlance or a VMXNET adapter, depending on which driver initializes it. With VMware Tools installed, the VMXNET driver changes the Vlance adapter to the higher performance VMXNET adapter.
  • E1000: An emulated version of the Intel 82545EM Gigabit Ethernet NIC. A driver for this NIC is not included with all guest operating systems. Typically Linux versions 2.4.19 and later, Windows XP Professional x64 Edition and later, and Windows Server 2003 (32-bit) and later include the E1000 driver.

Note: E1000 does not support jumbo frames prior to ESXi/ESX 4.1.

  • E1000e: This feature emulates a newer model of Intel Gigabit NIC (number 82574) in the virtual hardware. This is known as the “e1000e” vNIC. e1000e is available only on hardware version 8 (and newer) virtual machines in vSphere 5. It is the default vNIC for Windows 8 and newer (Windows) guest operating systems. For Linux guests, e1000e is not available from the UI (e1000, flexible vmxnet, enhanced vmxnet, and vmxnet3 are available for Linux).
  • VMXNET 2 (Enhanced): The VMXNET 2 adapter is based on the VMXNET adapter but provides some high-performance features commonly used on modern networks, such as jumbo frames and hardware offloads. This virtual network adapter is available only for some guest operating systems on ESXi/ESX 3.5 and later. Because operating system vendors do not provide built-in drivers for this card, you must install VMware Tools to have a driver for the VMXNET 2 network adapter available.
    VMXNET 2 is supported only for a limited set of guest operating systems.
    To determine if the the VMXNET 2 (Enhanced) adapter is supported for your guest operating system and vSphere ESXi version, see the VMware Compatibility Guide.

    Notes
    :

    • You can use enhanced VMXNET adapters with other versions of the Microsoft Windows 2003 operating system, but a workaround is required to enable the option in the VMware Infrastructure (VI) Client or vSphere Client. If Enhanced VMXNET is not offered as an option, see Enabling enhanced vmxnet adapters for Microsoft Windows Server 2003 (1007195).
    • Jumbo frames are not supported in the Solaris Guest OS for VMXNET 2.
  • VMXNET 3: The VMXNET 3 adapter is the next generation of a paravirtualized NIC designed for performance, and is not related to VMXNET or VMXNET 2. It offers all the features available in VMXNET 2, and adds several new features like multiqueue support (also known as Receive Side Scaling in Windows), IPv6 offloads, and MSI/MSI-X interrupt delivery. For information about the performance of VMXNET 3, see Performance Evaluation of VMXNET3 Virtual Network Device. Because operating system vendors do not provide built-in drivers for this card, you must install VMware Tools to have a driver for the VMXNET 3 network adapter available.
    VMXNET 3 is supported only for virtual machines version 7 and later, with a limited set of guest operating systems.
    To determine if the the VMXNET3 adapter is supported for your guest operating system and vSphere ESXi version, see the VMware Compatibility Guide.
  • Notes:
    • In ESXi/ESX 4.1 and earlier releases, jumbo frames are not supported in the Solaris Guest OS for VMXNET 2 and VMXNET 3. The feature is supported starting with ESXi 5.0 for VMXNET 3 only. For more information, see Enabling Jumbo Frames on the Solaris guest operating system (2012445).
    • Fault Tolerance is not supported on a virtual machine configured with a VMXNET 3 vNIC in vSphere 4.0, but is fully supported on vSphere 4.1.
    • Windows Server 2012 is supported with e1000, e1000e, and VMXNET 3 on ESXi 5.0 Update 1 or higher.

How to bulk upload/copy files and folders to SharePoint

One of the biggest challenges I have when migrating customers over to SharePoint is moving their files and folders.

On the surface this is a daunting task as you can’t just give SharePoint your folder structure and tell it to do the work for you, so below are some of the processes I use.

Option 1: Manually via SharePoint Web Interface

Recreate the folder structure in SharePoint and upload the files via SharePoint in batches doing a multiple file upload to one destination folder at a time using explorer view. Not much fun for anyone, but it can be done. This has also proved to be unreliable, some machines need patching to get this to work, so I have found myself spending a lot of time correcting errors with the WebDAV service in order get this to work… This is my least favourite method.

image

Option 2: Commercial Tools

Possibly look at a third party tool they will  cost you but will get the job done and probably with a few extra bell’s and whistles like applying metadata to SharePoint columns during the process. Some of the key companies to take a look at would be:

 

Option 3: Open Source Tools

There are some open source projects going around that claim to handle these types of bulk uploads, here’s a couple that look interesting:

https://spfilezilla.codeplex.com/ – This is my favourite – it really is just like FileZilla

image

http://spbulkdocumentimport.codeplex.com/

image

http://spfileupload.codeplex.com/

image

SharePoint Online, Sharing Content With External Users

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.

  1. Go to Admin > Service Settings > sites and document sharing.
  2. Do one of the following:
    • Turn on external sharing
    • Turn off external sharing

Image showing the on/off control for allowing external users access to your team site and documents.

SECURITY

  • 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.

  1. Go to Admin > Service Settings > sites and document sharing.
  2. Click Remove individual external users.
  3. Select the external users you want to remove, and then click Delete (the trash can icon).

Connecting a MAC to SharePoint inc O365

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:

  1. From Spotlight look for “Microsoft Document Connection” and open it.
  2. Click on the “Add Location” button in the upper left and choose to “Connect to a SharePoint Site…”
  3. 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.

Sequence-11 12 10-5 31 PM

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…)

Connect to Exchange Online using remote PowerShell

What do you need to know before you begin?

  • You can use the following versions of Windows:
    • Windows 8 or Windows 8.1
    • Windows Server 2012 or Windows Server 2012 R2
    • Windows 7 Service Pack 1 (SP1)*
    • Windows Server 2008 R2 SP1*

* You need to install the Microsoft .NET Framework 4.5 or 4.5.1 and then either the Windows Management Framework 3.0 or the Windows Management Framework 4.0. For more information, see Installing the .NET Framework 4.5, 4.5.1 and Windows Management Framework 3.0 or Windows Management Framework 4.0.

Connect to Exchange Online

  1. On your local computer, open Windows PowerShell and run the following command.
    $UserCredential = Get-Credential

    In the Windows PowerShell Credential Request dialog box, type your Exchange Online user name and password, and then click OK.

  2. Run the following command.

    $Session = New-PSSession -ConfigurationName Microsoft.Exchange -ConnectionUri https://outlook.office365.com/powershell-liveid/ -Credential $UserCredential -Authentication Basic -AllowRedirection

    Note   If you are an Office 365 operated by 21Vianet customer in China, use the following value for the ConnectionUri parameter: https://partner.outlook.cn/PowerShell.

  3. Run the following command.

    Import-PSSession $Session

NoteNote:

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.

Remove-PSSession $Session

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).

    Set-ExecutionPolicy RemoteSigned
  • The account you use to connect to Exchange Online must be enabled for remote Shell. For more information, see Manage remote PowerShell access in Exchange Online.
  • TCP port 80 traffic needs to be open between your local computer and Exchange Online. It’s probably open, but it’s something to consider if your organization has a restrictive Internet access policy.