Skip to main content

Restrict Users to Certain Computers

Limiting a user to certain logon workstations is a common administrative task. Doing this is a very repetitive  if you have to restrict users to certain computers. Even at that, Microsoft limits you to only 64 workstations when you are entering them in using the GUI. Although you can add additional computers in the AD attribute editor, it is still a huge (comma separated) pain!
To understand the problem, we will do it manually once. Open the user’s properties, go to the Account tab then click “Log on To”. Then add each computer one at a time. It will not take wildcards.



Comments

Post a Comment

Popular posts from this blog

Visual Studio 2012 / 2013 Update 1 2 3 4 Offline Installer

Visual Studio 2012 Update 2 was released about a week ago.  This update includes lots of fixes and some features – you can see the list   here .  The only problem with the update is that Microsoft does not offer an offline installer.  If you are installing this on your own PC or for one person, you may not have a need for one.  But…  if your entire team needs to install this (or you just want to have it for later for a PC rebuild, you can download all 1.8 GB and have an offline installer for you or your team to share.  Here’s how: Get the update from Microsoft  here . (updated with Update 4 link) Save the file to a folder. open the folder Pro tip – Shift + right-click the background of the folder and choose ‘Open command window here’ in the command window type  VS2013.4.exe /Layout (or VS2013.1.exe /Layout or VS2013.2.exe /Layout depending on your update) It will then ask you w...
Post a Comment
Read more

VMware ESXi 5.5 Purple Diagnostic Screen Exception 14 in SEsparse and LibAIO (LibAIODrainMergeQueue, LibAIOMergedIODone, SESparseAsyncDataDone) (2073516)

Symptoms VMware ESXi 5.5 host fails with a purple diagnostic screen You see backtrace similar to: cpu0:33101)@BlueScreen: #PF Exception 14 in world 33101:memMap-0 IP 0x4180182f4948 addr 0x4108fffffff0 PTEs:0x100088063;0x80000020ad5bf063;0x0; cpu0:33101)Code start: 0x418018000000 VMK uptime: 1:09:27:02.593 cpu0:33101)0x4123c535cb20:[0x4180182f4948]LibAIODrainMergeQueue@vmkernel#nover+0x150 stack: 0x4130002a85c0 cpu0:33101)0x4123c535cb80:[0x4180182f53fd]LibAIOMergedIODone@vmkernel#nover+0x211 stack: 0x412ec622ef90 cpu0:33101)0x4123c535cbb0:[0x41801802d21f]AsyncPopCallbackFrameInt@vmkernel#nover+0xe7 stack: 0x1 cpu0:33101)0x4123c535cbe0:[0x418018bb9798]SESparseAsyncDataDone@esx#nover+0x15c stack: 0x41300007b0c0 cpu0:33101)0x4123c535cc10:[0x41801802d21f]AsyncPopCallbackFrameInt@vmkernel#nover+0xe7 stack: 0x4123c535cc70 ...
Post a Comment
Read more

How to configure an IP address in Solaris 11

Oracle made a huge changes in the networking stack with Solaris 11. The use of many network related files have been deprecated in Solaris 11. Below are some of the files which are not used in Solaris 11 for persistent network configuration : /etc/defaultdomain /etc/dhcp.* /etc/hostname.* /etc/hostname.ip*.tun* /etc/nodename /etc/nsswitch.conf Network Configuration Profile Solaris 11 uses profile-based network configuration. It has 2 configuration modes : 1. Automatic   – Uses DHCP to obtain network configuration (IP address, router and DNS) from any of the connected ethernet interfaces. Do not support hot swapping of interfaces and IPMP. 2. Manual (DefaultFixed NCP)   – interfaces needs to be manually configured using dladm and ipadm commands. Also called as DefaultFixed NCP. Supports hot swapping of interfaces and IPMP. Configuring the IP address Step 1 : Set the NCP We would set the NCP to DefaultFixed profile in order to configure the IP address...
Post a Comment
Read more