In my organization, I had gotten a late start in to deploying Windows Server 2012 R2. (The culprits were versioning on our backup system of EMC Avamar and our versions of VMware vCenter.)
As such, I've just started deploying servers with it over the past 6 months or so.
Part of my standard server build process (or within my VMware templates) includes disabling User Account Control (UAC).
I'd hit the Start button, use the Search box and type in "user account control" and then go to Change User Account Control settings. I'd drag the slider down to "Never notify" and expect not to be restricted from doing things on my own servers. (Doesn't every administrator do this, really? What was Microsoft thinking with this "feature" anyways?)
Yet when operating with Server 2012, I was still being restricted. Trying to work with files within a system area like C:\Program Files, I'd would be unable to move files. "You'll need to provide administrator permissions" with prompts like this:
Finding the right keywords to Google were a little challenging, but ultimately I found the answer here: http://social.technet.microsoft.com/wiki/contents/articles/13953.windows-server-2012-deactivating-uac.aspx.
The GUI doesn't really disable UAC. You need to use a registry tweak.
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\policies\system
Change DWORD "EnableLUA" from default value of 1 to 0
You'll be rewarded for your effort with this pop up from the system tray:
"You must restart your computer to turn off User Account Control. Click to restart this computer."
Then after a reboot, lo and behold, you won't be hampered from managing your own server. Enjoy.
At work, I upgraded my laptop by replacing the hard drive with an SSD. Boy, did it make a nice improvement in performance. I took the purist approach and did a fresh install of Windows 7 and reinstalled all my applications.
Imagine my chagrin after a careful rebuild, only to find a number of DLL files in the root of my C drive. I deleted them, only to find them returning regularly.
Doing some Googling on one of the DLL names (such as tsgetxu6ag55.dll) wasn't turning up good results. I'd find lots of results to web sites that 'identify files' and would give me a lot of nonsense answers not clearly telling me if it was spyware, a legitimate file, or any useful info.
I stumbled onto what was going on once I started Googling what the file was. The properties of the DLL made mention of Tom Sawyer. Once I Googled that, lo and behold the answer came to light.
https://thwack.solarwinds.com/thread/55808
One piece of software I had reinstalled was SolarWinds IP Address Tracker. The newer version apparently isn't well-written, and it dumps many files in the root of your C drive. Well, that's helpful (NOT).
At that point, I searched and found an older version of the install and downloaded that. No more pesky DLLs appearing in the root of my C drive.
My organization has been moving from hosting our own Exchange and Lync/Office Communications on premise to Microsoft hosted via Office 365.
I had implemented Active Directory Federation Services (ADFS) and Lync Online about 18 months ago. ADFS had some challenges, but once I implemented it, it has been reliable. During implementation, I got on-premise pass through Windows Authentication working and off-premise sign in working. I had tested on versions of Internet Explorer, Mozilla Firefox, and Google Chrome successfully.
We're now readying to migrate to Exchange Online and away from our on-premise mail server. During testing, several of us in IT began realizing that sign-ins from Google Chrome was not working.
On premise, you would be prompted with a Google Chrome pop up dialog. You'd put in your credentials (email address and Active Directory password), and it'd take you right back to the logon prompt without error, and you'd never get in.
Off premise, you would be directed to our sign in page on our Federated Server Proxy server. Same behavior, enter credentials, return right back to sign in page without error.
Googling this error tipped me off to the problem being that Google Chrome not supporting Extended Protection. But I didn't know much about this, so I didn't know how to resolve the issue.
A case opened with Microsoft support got me directed to the fix, as documented here:
http://social.technet.microsoft.com/wiki/contents/articles/1426.ad-fs-2-0-continuously-prompted-for-credentials-while-using-fiddler-web-debugger.aspx
The article mentions problems when using Fiddler Web Debugger, but it's the fix for a Google Chrome issue as well.
It's a setting within IIS. The above link documents where the setting is within IIS to change it manually on each affected server (typically you have multiple ADFS servers for fault tolerance), or PowerShell commands to set this universally across the farm.
Once I made this change, my users can leverage Office 365 from any of the major browsers.
My organization transitioned from running Office Communications Server 2007 to Lync via Office 365. One of the benefits of the Office 365 implementation is that you can run applications like Lync while properly on the corporate network or while remote with Internet access.
Though our organization is strictly a Windows computing environment, there are a few people within the IT department that run Macs at home. As I was one of them, I wanted to explore running Lync on Mac OSX 10.9 Mavericks.
I downloaded Lync for Mac 2011, but was having difficulty signing in.
Investigating online, I found this article:
http://onlinehelp.microsoft.com/en-us/office365-enterprises/hh534388.aspx
But still, things weren't working:
A support call to Microsoft didn't yield the answer at all. I assumed it was a very minor detail, and that was correct. After days of nothing, I stumbled across the correct configuration.
Ensure you've got all the updates downloaded for Lync / Office 2011 for Mac.
Correct syntax for sign in is to use your email address in both the email address AND user ID fields. I was trying username or domain\username and getting no results.
In the Advanced options, you want Use Kerberos authentication unchecked, and the radio button to use Automatic Configuration, as shown below:
At that point, you'll be able to sign in.
