Re-Image your Surface Hub the easy way
[This is a copy of an article I wrote for my blog. you can find it over here including inline video http://www.skype4badmin.com/re-image-your-surface-hub-the-fast-and-easy-way/ ] I don't know about you, but I roll out a fair few Surface Hub devices for clients and the main issue is. Every time I pull them out of the box they are on a really old build of Windows Team. These older versions have some issues with certain scenarios and the newer builds change the look at feel of the device a little. So I always try to have the device on the latest version when commissioning a new unit for a customer. The issue was there was only two supported ways of doing this. Sign the device in to my test account online, force it to update and wait a few hours Re-image the device by "turning it off" during the boot process and forcing an online recovery (overnight) Both of these options are really frikken slow and have to be done onsite at the customers office. So our solution has been to carry some "Pre-imaged" SSD's with us to swap out when we arrive onsite. But the issue was we either needed to re-image these in our Surface Hub in the office, or use my dodgy hacked together CloneZilla server to prepare disks. So when I saw Y0av post this on his LinkedIn this morning I was really excited His post links to the first public build of the Surface Hub Recovery Tool from the Microsoft website. Download the SurfaceHub_Recovery_v1.4.137.0.msi (version number may change) file and install it on a PC with; Windows 10 1607 or better At least 10 GB free disk space on C: Some method of connecting a SATA disk that doesn't mask the drive ID, a list of tested USB to SATA cables is below. Here are the official requirements from help.txt included in the package Introduction: This tool was designed to help reimage your Surface Hub Solid State Drives (SSD) in a timely manner without calling for support or replacing the SSD itself. This will not fix physically damaged SSDs. You will need to call support if this reimaging tool does not restore your factory image. Time to download the recovery image is dependent on internet connection speeds. On an average corporate connection, it can take up to an hour to download a 10GB file. Requirements: Host computer running Windows 10 “Version 1607” or higher. Internet access USB -> SATA cable 10 GB of free disk space on the host computer SSDs shipped with Surface Hub or an SSD provided by Support as a replacement. Other SSD’s are not supported. Recommendations: High-speed Internet connection USB 3.0 or higher USB -> SATA cable Tested Make and model of cables: Startech USB312SAT3CB Rosewill RCUC16001 Ugreen 20231 Now we know we are good, we can install the tool by firing up the MSI and following the bouncing ball. Once the tool is installed, it pop up in your start menu as Microsoft Surface Hub Recovery Tool Launching the app will ask for admin rights and show a welcome screen. The Learn More link simply takes you to this PDF on how to remove and replace the SSD in the Surface Hub or you can watch the video below. Clicking on start will ask if you want to download the image for the Surface Hub. This gets stored in C:\Program Files\Microsoft Surface Hub Recovery Tool\install.wim and as Y0av reminded me, you can then just copy this WIM file between machines if you don't want to download it again. The download took me about 6 Hours on a 100mbit connection but once you have it, you have it right? Whilst you wait for that to download. Go shutdown your Surface Hub, turn off the AC power, remove the SSD and connect it to your PC/USB Adapter 30 Sec Howto here "http://www.skype4badmin.com/wp-content/uploads/2018/05/Imaging.webm" Once you have the drive connected to your PC using a supported method the tool should change from this To this; Note: The tool does do some sort of checking to see if its a Surface Hub drive, it seems to be looking specifically for a Lite-On SSD. I tried popping a generic disk in and it never showed up, so don't expect to make a fleet of spare disks to carry with you using this tool. Make sure your Surface Hub SSD is selected and hit Start. (No seriously. Make sure its the Surface Hub drive. This tool formats whatever you select, so if you don't want to lose your My Little Pony collection watch out) It gets stuck for a little while at a few different places. Don't worry, its still copying. If you really think its stuck, restarting it wont break the SSD, but it will be unusable until you re-image it. Once that's done, Pull the disk out and pop it in your Surface Hub. Then continue your build as per normal. 30 second how to here "http://www.skype4badmin.com/wp-content/uploads/2018/05/Imaging2.webm" Hope this helps. Thanks to Y0av and the Surface Hub team for making this available for us.Whiteboard App not starting on Surface Hub
Today (30.07.) we noticed that the Whiteboard App on our Surface Hubs stopped working. When the app is launched a window is displayed that login is in progress, but nothing happens. Anybody experiencing something similar or any suggestion on troubleshooting? I've already reinstalled the app.
Surface Hub 2S Overheating
Has anyone else out there come across the Hub 2S overheating? Basically the device will shut down mid use, then come up with a black screen with a thermometer icon. Eventually it will come back up normally but it's been disruptive to meetings. These are all the 55" 2S model using the "Microsoft Approved" Steelcase Roam wall mount. To me this seems like a design flaw with the mount itself. I know the Hubs have an airflow intake/output on the top and bottom of the back CPU component, but this mount essentially puts the device flush against the wall and any heat that radiates off the back essentially just redirects back to itself. Mainly curious if anyone else has come across this and what they might've done to remedy it.Surface Hub PSTN calling options?
This is probably as much an Office 365 question as a surface hub question, but I'll start here: We have surface hubs set up using room accounts in Office 365, and they currently have an E1 license assigned. If I want to enable people to dial in to conferences using the surface hub, do I just need to add the pstn conferencing option to the surface hub account? What if I wanted to make outbound calls from the hub? Can I do that by just upgrading it to an E5 license and adding the PSTN connectivity option? If so, does adding E5+PSTN to just one (or a few) accounts affect the rest of our accounts/O365 tenant or have any other consequences that may not be obvious?
"Something went wrong and we couldn't show that page" error in Teams for Surface Hub
I literally cannot get any other assistance for this error when I try and Google for it. It appears nobody has had it before. I start up my surface hub, it is domain-joined so I can login with a domain account on o365 and it syncs my calendar. However, when I launch Teams it consistently shows the bellow error. The Hub is up to date in terms of Quality and Feature updates. I have also tried uninstalling teams and reinstalling it, to no avail. The internet is working over the WiFi as I can launch Edge and browse around. I am out of options as to what else to try. Any thoughts?Surface Hub managed by Intune & Licensing via EMS
We have a few Surface Hubs in our organization which I'd like to add to intune. Obviously these devices should not be associated with a specific user, so I started looking into the Device Enrollment Manager (DEM) feature as a way to join the devices w/o tying them to a user. Reading the doc on DEM (https://docs.microsoft.com/en-us/intune-classic/deploy-use/enroll-corporate-owned-devices-with-the-device-enrollment-manager-in-microsoft-intune) leaves me with the impression that each device enrolled using a DEM requires it's own intune license. We get intune as part of EMS, which is licensed per user, not per device. Do we need to buy additional per-device intune licenses for each surface hub? Or, am I on the wrong track altogether? Is there a better way to enroll the Hubs in intune w/o a user association?
Surface Hub Certificate Deployment
Hi All, I was wondering if anyone here can help me? Last week I experienced the Windows 10 Team 2020 update and so far I really like the update regarding accessing content and the experience of signing in to the device (Surface Hub 2S). But what about certificate deployment via Microsoft Endpoint Manager? I noticed the https://msdn.microsoft.com/library/windows/hardware/dn904970.aspx but nothing about SCEP or PKCS certificate deployment? Can we deploy these certificates to the hub as we do it on our regular Windows 10 devices? Haven't got the chance to test it out myself unfortunately. Thanks!
