• Announcements

    • Terry (WGS)

      WGS Forums Will Close on January 31st 2017   01/18/17

      Hi everyone, We're coming up to We Got Served's ten year anniversary and I've been taking a good look at the site to work through some plans for the future. I wanted to give you all a couple of weeks notice that I'll be closing WGS Forums at the end of this month.  As you'll be aware, the forums were opened to support Windows Home Server users and have done so brilliantly, thanks to everyone's participation. However, with each day that passes, there are fewer and fewer WHS deployments out there, meaning that forum registrations and traffic has now dwindled. I've tried a few times over the years to test some forums on related or adjacent topics, however, they simply haven't caught on. It's clear that these were always going to be predominately Windows Home Server forums and, with the passing of that platform, they've served their purpose well. So, please take some time to archive anything you need over the next two weeks. Access to the forums will end on Jan 31st 2017. Many, many thanks once again for your participation and support here. It's been a great community! Very best wishes Terry
Sign in to follow this  
Followers 0
Terry (WGS)

How To Install Shlage Connect

1 post in this topic

If, like me, you're more used to hammering out fast network speeds on computers than actually using a hammer to, you know, <em>build stuff</em> then upgrading your abode with the latest smart home kit is going to require some thought - and a lot of research.
 
Sure, you can get an installer in to sort it out for you, but where's the fun in that?
 
Following last week's look at installing the Nest Learning Thermostat and Nest Protect Smoke and Carbon Monoxide Alarm, today, we bring you a video that covers a slightly more complex job - fitting a smart lock.
 
In this case, we've selected Schlage Connect. The good news is that the only tool you'll definitely need to fit the Schlage Connect is a Phillips screwdriver - that said, to get the job done perfectly, it'll be worth having a tape measure, flathead screwdriver, a pencil, a block of wood (yes, really) and a hammer on hand. Power drills aren't required, and indeed aren't advised as they can easily damage the lock.
 
Installing the lock is performed in a number of steps - before you get started, you'll need to check your door alignment with the door frame to ensure the deadbolt will be able to extend automatically into the frame. If you currently need to jiggle the door to close or lock it, the door or frame will need to be adjusted before you attempt to install the lock.
 
You'll also need to check a number of measurements and dimensions on the door and its frame - for example, the thickness of the door is an important factor in ensuring the lock will fit. Thicker doors may need a thick door kit accessory, which is available from Schlage. Make sure to take a note of your current crossbore and backset dimensions to ensure the new lock will fit any existing apertures. The bolt too may need to be adjusted to ensure it fits securely into the backset.
 
Once the bolt and strike is fitted into the door (a gentle tap with the hammer and block of wood is handy here to ensure the bolt is fitted securely) you can get to work fitting the electronic elements of the smart lock - the touchscreen assembly and support plate. Drop in the batteries, set up the touchscreen locking codes and you'll be ready to test.
 
Sounds easy? Well, to many I'm sure it is, but if it's your first time disassembling a door lock and installing a new one then you'll want to take it step by step. Fortunately, Schlage has produced a detailed step by step installation video to watch in advance and has published <a href="http://www.schlage.com/en/home/support/how-to-center/installation-manuals-templates.html"target="_blank">an installation guide on their website</a> - both great sources of research before you take the first step.
 

Share this post


Link to post
Share on other sites

Upgrade to a WGS Supporter Account to remove this ad.

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!


Register a new account

Sign in

Already have an account? Sign in here.


Sign In Now
Sign in to follow this  
Followers 0



Upgrade to a WGS Supporter Account to remove this ad.



  • Posts

    • Hi - I'm now on Lights-Out 2, but the problem persists. Today 3 client computers suddenly shut down after a Lights-Out backup, whilst they were in use (but the users were away from the keyboard so never saw the warning message). All 3 computers had missed their previous backup (scheduled during Friday night). The 3 computers were automatically backed up during the day today, Monday (their next scheduled backup was set for Monday night). At the end of the backup they shut down & the users lost work. I'm trying to create a situation where... Each evening, the client computers are put to Sleep. During the night, the server wakes up the clients in turn, runs a Lights-Out backup, then shuts down the clients. When all the backups are done, Lights-Out puts the server to Sleep. In the morning the clients are re-started, the server wakes up, and the day begins as normal (I like the idea of the clients being restarted regularly). If one of the client computers can't be woken up during the night (the user had accidentally shut it down at the end of the day, or took it home with them), I don't mind what happens next: either a 'normal' Windows server backup during the day; or nothing happens until the next scheduled night-time backup. But these unexpected daytime shutdowns are making me increasingly unpopular - is there any way to avoid them during the daytime when everyone is trying to work normally? many thanks, Simon
    • Please contact support@green-it-software.com and I can send you a copy.
    • Hi, I am looking for these drivers HpMssServiceSetup_v1.0.6 but the dowmload link is dead. Does anyone have a working link please. Thank you.
    • That guide is for installing Exchange on a Server Essentials network, not necessarily installing both services on the same server, which isn't a good idea at all to do (as SBS with Exchange 2007/2010 was a good example of how poorly both AD and Exchange run when both are on the same server), nor is it supported by Microsoft.  Exchange 2016 initially had compatibility issues when installed on Server 2016 until Microsoft's server team came up with KB3206632 and the Exchange team released December 2016's quarterly update (CU3 or 4). Your IIS Reverse proxy will only (currently) be supported on Windows Server 2012/R2, as you've no doubt discovered, the Application Request Routing version and update only support 2012/R2. I know it works for 2012 R2 because I'm running Exchange 2016 CU4 on Server 2012 R2 on my domain that also includes a Server Standard with Essentials Role installed (5 VMs:  2 Domain Controllers, Exchange 2016 CU4, Server Essentials and a Reverse Proxy server all running 2012 R2 using ARR 2.5 -- the ARR Reverse Proxy allows me to share Exchange, Essentials RWA and my QNAP on 443), but thus far, I haven't seen anything for Windows Server 2016.  ARR 3.0 might work with Server 2016, or your other alternative is to deploy another server running 2012/R2 and use ARR 2.5.
  • Popular Contributors