May 8, 2017 - 11:07, by Steven Van de Craen -
October 16, 2014 - 22:04, by Steven Van de Craen -
Ever since I built my dev VM with SharePoint 2013 and least privileged installation it had this issue where no user requests entries (Info, Error, Unexpected, …) would get logged to the SharePoint ULS logs. At first I blamed it on SharePoint of course, but CU after SP after PU did not fix my issue so it couldn’t be that. And no other of the environments I set up were affected by this issue.
What _did_ get logged:
- Every other process (Distributed Cache, OWSTimer, NodeRunner, …)
- Central Administration requests
- Service Application requests
My least privileged installation is pretty basic stuff:
Farm Administrator is used for the Timer Service and Central Administration AppPool Identity.
Installation account. Requires local admin rights on SharePoint and dbcreator and security admin on SQL Server.
AppPool Identity for SharePoint sites
AppPool Identity for SharePoint Service Applications.
Search Content Access account for indexing data.
Super User account for object caching.
Super Reader account for object caching.
User Profile synchronization account to Active Directory. Requires "Replicate Directory Changes" on the domain. http://technet.microsoft.com/en-us/library/ff182925.aspx#permission
Since this is a dev VM you can imagine this being a real pain troubleshooting bugs and flow. Until today, because on one attempt I changed the Service Account for the Content Application Pool (DOMAIN\sp_contentapps) to the Farm Administrator and POOF! my logging had returned:
So what was wrong with this DOMAIN\sp_contentapps? I decided to fire up the awesome ProcMon (filter on User Name, exclude all “Success” entries) to see what exactly was going on:
It was trying to load that user’s Windows profile from disk but somehow ended loading up a temporary profile:
Look for Event ID 1511 in the Application Event Log and you’ll find a corresponding entry:
Microsoft have provided us with a few options to resolve this in the following KB Article: http://support2.microsoft.com/kb/947215/en
- Open the Registry Editor
- Navigate to HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\ProfileList
- Find the key starting with S-1-5 and ending with .bak
- Remove the .bak suffix (if you can’t rename because a key already exists you have to rename the latter in two steps so it ends up having the .bak suffix)
- Click on the renamed key (without suffix)
- Set the value for “RefCount” to 0
- Set the value for “State” to 0
- Log in & out with the account (you may need to temporarily grant it access to do so) so the profile folder gets created
- Ensure that the correct profile folder is present
- Ensure that the application pool is started (likely it failed after the reboot because of the missing profile folder)
- (Optional) Clean up the “.bak” registry key and corresponding temporary profile folder
So conclusion; I probably at some point deleted that profile folder for who knows why, but it had some unforeseen consequences…
October 3, 2014 - 21:26, by Steven Van de Craen -
Today I decided to look into Windows 10 Technical Preview without safety net and run it on my main work machine. No real issues so far, except connecting to our corporate network via Cisco AnyConnect (version 3.1.04059).
Failed to initialize connection subsystem
This can easily be resolved by running the VPN client in Windows 8 Compatibility Mode. Just edit the shortcut properties and set compatibility mode. Then restart the client and try again.
If you still run into issues try the following registry trick you might had to do in Windows 8 as well:
- Open Registry Editor (Start > Run > Regedit)
- Navigate to HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\vpnva
- Change the value of the “DisplayName” key by removing the garbled characters before the name “Cisco…”
Hope this helps!
October 2, 2014 - 11:56, by Steven Van de Craen -
I’ve often worked on SharePoint environments where I accidentally got kicked or kicked others because we were working with the same account on the same server via Remote Desktop. By default each user is restricted to a single session but there’s a group policy to change this.
In Windows Server 2008 you had a UI for this, but since Windows Server 2012 you have to do this via gpedit.msc. This basically enforces a setting in the Windows Registry which you could do directly:
- Open Registry Editor (Start > Run > regedit)
- Navigate to HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Terminal Server
- Ensure the DWORD fSingleSessionPerUser exists and is set to 0
Or -even easier- create and run a .reg file with the following content:
Windows Registry Editor Version 5.00
Here’s a quick link for you: ALLOW_MULTI_RDP_PER_USER.reg
December 5, 2012 - 13:41, by Steven Van de Craen -
There is a lot of ink already on the subject of converting Microsoft Virtual Machines to VMWare Virtual Machines, but I’m writing down what worked for me to get it up and running.
VMWare vCenter Converter
Download it and install it. If you’re not carrying multiple machines then install it on your Windows 8 (that’s running your Hyper-V machines). I’m doing that, because a different machine adds quite some hassle when trying to connect.
Run as Administrator
Configure the Converter client to Run As Administrator.
Connect to IP address
When connecting to the Hyper-V server, you might want to use the IP address of the machine (eg. 127.0.0.1) to avoid some hassle with SMB restrictions. I’m sure you could as well solve those, but IP works fine as well.
Unable to obtain hardware information for the selected machine
If you get this, and believe me you will, first make sure the selected machine is powered off. But even then you’ll likely run into this. The fix is pretty nasty:
Grant “Everyone” Modify permissions on the folder containing the VM disks (.vhd).
Another thing to verify is that your Virtual Machine hard disk is not using the newer VHDX format introduced in Windows 8 and Windows Server 2012. This will also result in the above error.
You'll need to edit and convert your disk to the VHD format. If you have snapshots and want to keep them, you can export the snapshot and import it again as single VHDX file, which can then be converted...
When you get to this screen, make sure the path to store the converted machine on is a UNC path.
Easiest here is to create a temporary folder and grant the specified account Write permissions.
When you pass all these hurdles you’ll get to a few more configuration screens like the one below, but really nothing will stop you now from converting that machine, let alone insufficient disk space ;)
So why am I converting you ask ? No, I’ve not yet given up on Hyper-V. Sure it has less features but so far I haven’t really missed any of them. I can get around using Remote Desktop and Internet Connection Sharing just fine. I’m only creating these VMWare images for some of my colleagues that run VMWare (either they can’t be convinced or don’t have the right CPU to run Hyper-V 3.0 on Windows 8).
Another really useful guide on this is the following blog post: Converting Hyper-V to VMWare
March 17, 2012 - 10:16, by Steven Van de Craen -
A few days ago I tweeted about having moved to Windows 8 Consumer Preview as main Operating System. So far still really happy with it.
My previous OS was Windows Server 2008 R2 with Hyper-V for virtualizing my SharePoint development environments. I had tweaked Windows Server as much as possible to be more of a desktop OS than server OS, but the fact remained that it just hadn’t optimized audio and video drivers. Surely they’re adequate to perform basic tasks, but there still was a little bit mouse and audio stuttering when a YouTube started playing, let alone playing a recent game such as Modern Warfare 3 or Skyrim. For those I kept a Windows 7 dual boot environment around.
The main driver to move to Windows 8 for me was to have Hyper-V. Mind you that it’s not a straightforward path to migrate your Windows Server 2008 R2 images. I tried the export and import feature; it complained about not being able to use Saved State but it kindly asked me if it could delete that, I said yes. The import went fine but still I could start up a snapshot due to some obscure error. Perhaps this is a beta issue and will be fixed in RTM.
I decided to make a copy of the entire VMDISK folder and then just create new Virtual Machines in Windows 8, linking to existing disks (.vhd and .avhd). Nothing new here but note that you can use the “Edit Disk” functionality to merge a snapshot disk with its parent disk.
So I now had “base” images of all my machines in Windows 8 and booted them up. The next thing you’ll probably do is install the new Hyper-V Integration Tools in each virtual machine. This will upgrade the HAL in the VM.
Hyper-V networking has changed in 3.0 as well, using network bridging to overcome some issues from the past. This new Network Adapter will be seen as a new NIC in the VM as well, so you’ll have to reconfigure any static IP’s you had before.
A final thing is Windows Activation. Since you’re using a new HAL in the virtual machines, Windows will need to reactivate.
After that you can shut down the machines and make a base snapshot to start each new project on.
Note: the general experience might improve in the RTM version, but if you’re using Hyper-V then you’re probably tech savvy enough to migrate the more difficult way
A lot has been said about the Metro UI already. In Windows 8 there are two UI modes: Metro and Desktop (as I call them). Metro is the thing for mobile devices, slates and is very slick and touch driven (even if you can still operate it with a mouse and keyboard). Desktop mode is what we all know from Windows 7 and before.
Applications come in two forms; either it’s a Metro app (downloaded through the App Store), or a Desktop app (every piece of Windows software that is known to man). You can have a split screen of two apps.
The Start menu has been removed in favor of the Metro Start Page.
A lot of the navigation now happens by moving the mouse to a screen corner
- Top Left will show the Metro Task Manager for app switching or dragging split screen
- Bottom Left (where the Start Menu used to be) jumps to the Start Page
- Top Right or Bottom Right will bring up the Settings Menu
I had the Windows 8 Developer Preview and there were some tools that allowed you to disable some Metro features so that you basically only had Desktop Mode (with Start Menu). It seems Microsoft is really pushing Metro and none of the tools to date allow this on the Consumer Preview.
I’m fine with using Metro since it’s a lot like my Windows Phone. I can get used to the Start Page by rearranging tiles, but in Desktop mode I do want my Start Menu back !!
ViStart to the rescue. Designed for Windows XP it renders the Vista or Win7 Start Menu with most functionalities you’d use it for. During some shutdowns it throws a buffer overrun or other error, but in general it works really great on Windows 8 and should Microsoft decide to permanently drop the Start Menu then this is your friend!
The road goes on
It’s been only a few days since I installed it. I’m very pleased with overall performing and hope it will remain stable. Should things go wrong then I have an image of my previous OS at hand.
January 5, 2011 - 15:22, by Steven Van de Craen -
So today I ran into an issue on my working environment that I couldn’t access any shared folders, even if the share was a local folder and I had all available permissions.
My colleague Davy Coolsaet found this thread describing the issue.
I verified in Device Manager and I did indeed have hundreds of Microsoft 6to4 Adapters installed.
Removal of the adapters can be scripted using the devcon.exe utility that can be found here for x86 and ia64. If you need the amd64 version you must download the Windows Driver Kit in order to obtain it. For future ease I have packaged all versions here: devcon_all.zip
devcon remove *6to4mp*
Next make sure you install this hotfix to avoid this happening again in the future.
Finally reboot the system and you’re done !
Thanks a million, Davy !!
July 22, 2009 - 20:48, by Steven Van de Craen -
I would have preferred if Win7 RTM came sooner so that I could avoid migrating from Beta to RC and then from RC to RTM but no point to keep on whining about it :) So I decided to install the 64 bit issue of Windows 7 Release Candidate. I love how smooth those Win7 installs are. Very little interaction is required and the system correctly detects and installs my hardware.
Date: Wed Jul 22 20:41:09 UTC+0200 2009
Message: Unspecified error.
Tried the compatibility mode, tried the no-addons approach, no luck. However then I noticed there was another link in the Start Menu for Internet Explorer that read “Internet Explorer (64-bit)”. I tried it and poof: OWA behaved as a perfect citizen ! Joy !