Ask a question

User

Questioning Whether WSE 2016 Essentials Was the right Migration Target

I purchased the documentation to migrate from SBS 2011 to Exchange 2016 running on Server 2016, with the WSEE role installed on a DC.

I'm starting to question whether that's the right place for us to end up. I am not sure I fully understand everything WSEE offers. The connector software required to be installed on end workstations gives me pause.

Here's what I would like (or would be nice to have):

  • A convenient portal for end users to use to remote into their work PCs, as they currently can do via SBS 2011's portal and RDP gateway service.
  • An admin console that will automatically provision a user's Exchange mailbox when the user is created, in much the way the SBS 2011 wizards do when adding new users.
Here's what I don't want/need:
  • To be forced to use pre-configured WSE 2016 GPOs that restrict my management flexibility. We already have a significant investment in our current GPOs and OU structure and many of the pre-fab SBS GPOs are not in use in my environment.
  • To have special connector software with a user interface on end-user workstations. What exactly does this software do? I've been googling but so far haven't seen a good explanation of what its purpose is and how it's meant to be used. I'm having a hard time imagining anything useful enough to warrant that added complexity.
  • Backup of end-user workstations. We don't need this. We've been using folder redirection for years (and not to the SBS box but to a separate file server.
  • Windows 10 feature/version updates breaking the connector software, requiring workarounds or reinstallation. 
Is using WSE 2016 an all-or-nothing proposition, or can I choose to implement the parts that are useful to me and ignore the rest? 

asked12/27/2019 17:39
39 views
Add Comment
Bill Swan

Hi Bryan

Its a great replacement for SBS 2011. Guide is very comprehensive to move from an unsupported environment ( Jan 2020). Guide is very helpful assisting minimal downtime for site.  Only issue of it all is transfer of data is the only downside.. Don't want users accessing old share when transferring to new share and no matter which way it is done it does take sometime. I disable old shares so users cannot change data till its in new server but then mapped drive has to be done. 

  1. Users to remote into pcs no different .. HOWEVER if user uses IE then cached credentials in IE gives a little hiccup and it needs clearing. F12, network tab and clear cache. However I get clients to use RDP gateway straight to user pc.
  2. You don't have to use the GPO wizard, folder redirection the main benefit, just skip it if you wish.
  3. Connector software is mainly for the health monitoring, never used the ' launchpad ' , of many users I look after only one asked what it is for and then not interested. Just a different way to perform functions when known ways still work.
  4. Guide shows howto turn off backup and if don't need it can ignore.
  5. There was a blip from one version W10 to another but recent updates seem ok. Make sure windows 10 is fully upto date before installing connector.. its a god send ensuring users look after their pcs.. I teach them so they know what to do on their home pcs.

Finally, depending on Exchange / Outlook version, split DNS and autodiscover is a must.

Hope it helps.

Bill

Last Activity 12/28/2019 19:10

No answers found

Add an Answer