I then went to mycompany.remotewebaccess.com/remote and the site then came up fine. 

This is the workaround I found to fix this issue.  

Step One: Open Internet Information Services (IIS)

Step Two: Go to Sites > Default Web Site > HTTP Redirect

Step Three: Check the box Redirect requests to this destination: “Enter company URL with /remote at the end.

Check the box “Only redirect requests to content in this directory (not subdirectories)”

Step Four: Click Apply    You should be set now. If this doesn’t work for you, restart the Default Web Site.

I found this forum thread on TechNet with other experiencing the same issues. It wouldn’t be a bad idea to comment on that thread. That will help bring it to Microsoft’s attention. I believe this is a bug with Server 2016. Server 2012 and 2012R2, this worked perfectly without having to do this HTTP Redirect.   I will keep you posted if I learn more.

Please comment below if this helped you. You can find me on Twitter and check out my YouTube Channel. 

I am running the Windows Insider build,so there is a chance that some of the features won’t make it into the final Anniversary Update release. Enjoy!

This was posted by techspeeder.

Typically, I join the computer to the domain using the Windows Server Essentials connector tool. Here are the steps I use below.

Step One: I went //servername/connect and installed the connector software. I rebooted the computer when I was prompted to do so.

Step Two: The computer rebooted and started booting into a _clientsetup_$ profile. The computer took a minute or two but it logged into the _clientsetup_$ profile. I was then prompted to enter the user’s credential’s to connect the computer to the domain.

Step Three: I entered the credentials, and then I selected “Setup this PC for myself”. Instantly, the connector software froze and said: “Windows Server Essentials Connector” has stopped responding, end program. The Connector software closed but the computer kept me logged into the _clientsetup_$ profile until I rebooted the computer.

I then logged into the computer. The computer was joined to the domain but the Connector software was not installed.

I thought this may have been a one-off issue so I tried joining the computer again. Once again, I was greeted with “Windows Server Essentials Connector” has stopped responding. I will list below all the things I tried -none of them worked.

• I tried to join the computer to the domain with the admin credentials instead of the user’s credentials.
• During the Connector software setup, I selected “Setup this PC for myself and others” instead of “Setup this PC for myself.
• I checked Event Viewer. It said clientdeploy.exe has stopped working. Right before that error, I got a .Net framework error as well. I ran the Microsoft .Net Repair Tool. The .Net repair tool didn’t fix my problem, so I turned off .Net framework in “Turn Windows Features On or Off” in Windows. That didn’t work as well.
• Installed the Windows Server Essentials R2 Connector from Microsoft’s website.
• Right-clicked on the connector file and “Ran as an Administrator”
• Connected the laptop via an Ethernet connection (instead of wireless) and ran the wizard.
• I joined the domain manually and then tried to run the Connector software. It still failed.
• I created a new local admin profile and ran the Connector wizard from that profile.
• I rebooted the server.
• Disabled IPv6 on the laptop- we thought maybe there was a conflict
• Renamed the laptop multiple times
• I checked the server. The computer showed up under the devices tab in the dashboard as being on the domain.  However, the computer showed offline and the server didn’t know what OS was installed or anything about the client.

I decided to check the Connector software’s log and see if I could learn anything. I browsed to C:\ProgramData\Microsoft\Windows Server\Logs folder. I opened the log and found something very interesting. This is what the log read:

[3704] 160419.115344.2661: ClientSetup: LookupAccountSid (computerName = [], sid = [S-1-5-32-555])
[3704] 160419.115344.5319: ClientSetup: !!!FATAL!!! Unhandled Exception: System.ComponentModel.Win32Exception (0x80004005): No mapping between account names and security IDs was done
at Microsoft.WindowsServerSolutions.ClientSetup.NativeMethods.LookupAccountSid(String computerName, SecurityIdentifier sid)
at Microsoft.WindowsServerSolutions.ClientSetup.User.AddRoles(UserRoles userRoles)
at Microsoft.WindowsServerSolutions.ClientSetup.ClientDeploy.ConnectorWizardForm.m_wizardPageSetupForMyselfOrOthers_

I found this error had to do with a user account issue. I found on Microsoft’s MSDN website that the S-1-5-32-555 SID is a remote desktop users local group. Apparently, the connector was running into some problem with the remote desktop user group.

After doing some searching, I found a forum thread that was detailing the exact same thing – except those computers were running Windows 8. The forum mentioned that the computers that were having issues were mostly computers that had been upgraded from Home to Pro. This stirred my thinking and I remembered that this laptop had been upgraded from Windows 10 Home to Windows 10 Pro.

I am quoting this from another forum thread on Technet.

Based on the ClientDeploy.log above, it looks like it successfully looks up the local [Administrators] group (SID [S-1-5-32-544]) and successfully adds the “Me” account (SID ending in -1116) to that group.  It looks like it blows up when it tries to get the name for SID [S-1-5-32-555], which is the well-known SID for local group “Remote Desktop Users”.

Coincidentally, I noticed that in looking at the Computer Management console, the Windows 8 Pro computer (“moved up” from Windows 8) doesn’t have that local group for some reason.  A second Windows 8 Pro computer that I have, which was Windows 8 Pro out of the box, does have that group.  Thus, at this point, I’m still suspecting a bug in the process that “moves up” Windows 8 to Windows 8 Pro.  While it may or may not be related to this specific problem, why would the “Remote Desktop Users” local group (as well as several others that should be present in Pro) be missing?

Microsoft later addressed the Windows 8 Home to Pro upgrade issue with this update rollup. I know the article I referenced is dealing with Windows 8, but I believe this is also an issue with Windows 10. Somewhere in the upgrade process from Windows 10 Home to Windows 10 Pro the “Remote Desktop User” local group got missed.

I ended up joining the domain manually and just skipping the Connector software for now. If anyone has run into this issue as well, please let me know in the comments below. Better yet, if someone knows a fix or a workaround for this issue that would be awesome! I hope Microsoft addresses this bug in an upcoming update like they did with Windows 8.

I found this article that may fix the missing user groups after a Windows 10 Home to Windows 10 Pro upgrade. I didn’t have time to test this solution but it may be worth a shot.

This was posted by techspeeder.

I found that the quickest and simplest way to get these lockscreen images is to download the SpotBright App from the Windows 10 store.

This app does exactly as it advertises. It downloads the daily lockscreen images that Microsoft uses on Windows 10 desktop and mobile.

Once the app is downloaded just do a Fast Search and it will find all the current Spotlight images that Microsoft currently offers. Just download the images files and you are set! The cool part is that each photo has a mobile and desktop version. You get to choose what photo to use according to what device you want the photo on! 

Let me know if you enjoyed this post. Please follow me on Twitter and check out my YouTube Channel.

Kudos to the developer who made this app. Thanks

Step One: Open Outlook.

Step Two: Find the Microsoft Outlook icon in your icon tray. You may need to click the “up” arrow. 

Step Three: Right-click the Microsoft Outlook icon and uncheck the setting ” Hide When Minimized“. With that setting unchecked your problem will be solved.

If this helped you please leave a comment or share this tip with your friends.

This was posted by techspeeder.

Source: Microsoft Community 

Another technician looked at the problem first so I will list the steps he tried.

Step One: Turned off AntiVirus ( Avast ) , Uninstalled Covenant Eyes (Software)

Step Two: Deleted Items in C:\Windows\SoftwareDistribution\Download

Step Three: Ran Command Prompt wuauclt.exe /updatenow

After the above steps were completed, the computer still returned error code 8007002C-4000D.

I decided to take a look at the issue. I decided to “Google” the issue first to see if anyone else had a fix for this problem. I found this Microsoft forum full of people having this issue. I scanned over the thread and found a general consensus that it seemed to be a software giving us upgrade problems. Here are the steps I tried.

I uninstalled Avast and Covenant Eyes software.

I ran system file checker sfc /scannow . System file checker didn’t find anything amiss.

Next I ran msconfig and went to the startup tab. Under the startup tab I removed all software from starting up.

I began the Windows 10 upgrade. Much to my relief and happiness the Windows 10 upgrade was successful.

Conclusion: From the troubleshooting things I tried, I believe unchecking all software from startup is what fixed this issue. Previously, Windows 10 would almost install but after the reboot the software would try starting up. One of the software items I unchecked must have been giving me my issues.

I hope these troubleshooting tips can help you out. Please leave a comment if you have trouble upgrading your computer to Windows 10 as well.

This was posted by techspeeder.

When I clicked on the “View Warning Details” I got some more details.

There was an error that read “unexpected error” with a yellow sign beside it as well as a “messaging management” error with a red X beside it.

I closed out of the user account setup wizard. The user account was created but the email address wouldn’t be. If you are receiving this error, here is the fix I found.

Step One: Go to Control Panel > Programs > View Installed Updates . Search for update, KB2506143. If it is installed, uninstall the update. You will need to restart the server once the uninstall is complete.

Step Two: After you restart the server, open the SBS console again and try creating a user account. The setup wizard should complete successfully this time.

After I restarted the server, I opened the Windows Small Business Server Console 2011 and tried adding a user account. I was able to add the user account and email address without a problem!

Conclusion: After Update KB2506143 (Power Shell 3.0) the functionality to add a new user account with an email address was broken with servers running Exchange 2010. After the uninstall of that update, everything worked again. Here is another article you can refer to about this issue.  Feel free to post in the comments if you have another suggestion or if a fix has been issued. Thanks

This was posted by techspeeder.

Hat Tip: jaredr80

Device: Konica Minolta Bizhub C252

Username: Administrator

Password: 12345678

Source: http://www.copytechnet.com/forums/showthread.php/6742-Konica-Minolta-Bizhub-C450-Admin-password-locked

******************************************************************************

Device: Kyocera taskalfa 300ci

Username: administrator

Password: admin00

******************************************************************************

Device: EnGenius ECB600

Username: admin

Password: admin

Default IP address: 192.168.1.1

******************************************************************************

Device: Aastra 6757i CT

Username: admin

Password:  22222

******************************************************************************

Device: Buffalo AirStation N600 WZR-600DHP

Username: admin

Password: password

Default IP address: 192.168.11.1

******************************************************************************

Device: D-Link DAP-2553

Username: admin

Password: there is none

Default IP address: 192.168.0.50

******************************************************************************

Device: OKI MC561

Username: Admin

Password: aaaaaa

******************************************************************************

Device: OKI MB770

Username: admin

Password: 123456

******************************************************************************

Device: Netgear ProSafe VPN FVS318v3

Username: admin

Password: no password

******************************************************************************

Device: Brother MFC 9840CDW

Username: admin

Password: access

******************************************************************************

Device: Sharp AR M277

Username: admin

Password: Sharp (case-sensitive)

Source: http://www.copytechnet.com/forums/sharp/21286-sahrp-ar-m277-scan-user-name-password.html

******************************************************************************

Problem: When installing the Windows 8.1 update, the update would install until it got to 3% and then it would error out. This is the message it gave: Couldn’t update to Windows 8.1 . . .  Sorry, we couldn’t complete the update to Windows 8.1. We’ve restored your previous version of Windows to this PC.  0x80070005-0x4000D .

Solution:

Step One: Browse to this location: C:\$Windows.~BT\Sources\Panther and you will find a Setuperr log file. This log file contains the errors your computer ran into while upgrading the PC to 8.1.This is what my log said: User profile loading error.

Step Two:  Oddly enough, the c:\Users\Brent was an old user account that they weren’t using, and it corrupted for them. Since the user profile, Brent, was corrupt, I cut that whole user folder to the base of C:\. We then tried the upgrade process and it worked like a charm!

If this helped, like us on Facebook. This was posted by techspeeder.

The laptop would install the update and then I would restart. However, during the reboot it would do its normal update process “Configuring Windows Updates”, it would get to about 35% and then say “Failure Configuring Windows Updates, Reverting Changes”.

I searched online for some help but no one had a good solution for this issue. After a bunch troubleshooting this is the solution I found.

Step One: On the laptop, I went to Control Panel > Programs > Turn Windows features on or off. I unchecked the Internet Explorer 11 box and disabled the browser.

( On a side note) I don’t know why it said Internet Explorer 11, it should have said IE 10 since that was the version I was on. That could be one of the reasons the security update for Internet Explorer 10 didn’t want to install.

Step Two: I then went to Windows Update and installed the Security Update for Internet Explorer 10. The update was installed, so I restarted the computer. I waited -with crossed fingers – and it went through the “Configuring Windows Updates” and installed just fine!

Step Three: I then went back to the Control Panel and found the “Turn Windows features on or off” and checked the Internet Explorer 11 box. Once Internet Explorer was installed again, I typed iexplore in the search box and opened IE 10. It had updated the browser. I then checked my Windows Updates again and installed Internet Explorer 11.

I hope this helps you, if it did show your appreciation by liking my Facebook page.

This was posted by Techspeeder.