I’ve found that with a Terminal Server environment running on Windows Server 2008 R2, in a Windows 2003 Domain, with per-user client licensing; I was getting error 4105 in Event Log when remote users would log in. This error description says The Terminal Services license server cannot update the license attributes for user “<name>” in the Active Directory Domain “<domain>”. Ensure that the computer account for the license server is a member of Terminal Server License Servers group in Active Directory domain “<domain>”. Even though the License Server is already a member of that group. The real problem in my case was that the group doesn’t have the necessary permissions in the domain on the user account objects. Of course this error will probably more commonly occur when the Server is not actually a member of the group like it’s supposed to be…but if like me, you’re sure that’s already done, then this might help.
- Open user account properties in AD, and click on the Security tab.
- Select the “Terminal Server License Servers” group from the list, and check the “Allow” checkbox next to the properties “Read Terminal Server License Server” and “Write Terminal Server License Server” attributes. Click Apply to save.
In our Domain this group was already added for 2 ’special’ properties on the user accounts, but not this attribute. I discovered the difference, because new user accounts created were working without the error, and they in fact were created with the above permissions already granted on them.
I found this solution online posted by “FTPServerTools” It lets you show devices in Device Manager, which are not currently physically connected to the system. You might want to do this if for instance you want to remove a driver installed on the system for a device, but the device isn’t available for whatever reason. (Such as in my case where a driver was crashing the system when the device was connected, but the driver couldn’t be ‘replaced’ in the GUI because it doesn’t show up when the device is not connected!)
Add in your system environment variables (Setting in User Environment variables worked for me too) the variable:
DEVMGR_SHOW_NONPRESENT_DEVICES
set it’s value to: 1
reboot your machine (A logout was all I needed…)
goto your device manager
show all hidden devices (menu)
Now you can see all devices you ever installed including the ones that still have drives installed but are no longer in use. So dont be surprised if you see multiple monitors or haddrives and so. Just simply delete the network card you no longer have and you are done.
Without this environment variable you will not see the devices that are no longerpresent.
Windows Server SP1 and Windows XP SP2 (and probabably other versions of Windows) seem to have a limit on the ‘length’ of the ‘DNS Suffix Search List’ that can be defined. I ran across this when setting a list of DNS Suffixes via Group Policy. The entire list as configured in Group Policy was passed to the client machine, and displayed fully when running the command “ipconfig /all”; however the last entry was getting truncated when performing DNS lookups from most programs. I examined the list and discovered that the cut-off character was the 255th character in the list… I doubt that’s a cooincidence! Note that in Group Policy the list of suffixes is defined as a comma-seperated list of domain names. The commas do count in that 255 character limit. I blame the DNS service, as the Group Policy and Regisistry, and the output of ipconfig /all all display the full list of suffixes.
More information on setting the DNS Suffix Search list can be found in this MS KB Article: http://support.microsoft.com/kb/275553
I embedded Gallery 2 inside my Wordpress site using WPG2 (at the time of this writing v3.0RC1 – Dated July 20th 2007). I modified the wpg2.css file with the following code, to modify a slightly modified version of the ‘classic’ gallery theme. Major modifications to the theme itself include removal of several ‘blocks’ (like the footer and header) and the moving of the sidebar from the left to the right side of the page. Continue reading ‘Embedded Gallery’
Situation: Configure Cisco DHCP server to provide Network Call Processor (NCP) IP address to 3Com NBX phones using DHCP option 184.
Resolution: 3com NBX phones can receive their NCP (Network Call Processor) server from DHCP, by using DHCP Option 184. The settings I found that work best, are to simply provide the hex values for option 184. Continue reading ‘3com NBX DHCP Option 184 – NCP Server’
