RSS

Monthly Archives: September 2011

Windows Multipoint Server 2011 and HP T150 Thin Client

HP T150

I just received the new HP MultiSeat T150 Thin Client from HP. I am intending on testing this device with the MultiPoint Server 2011 offering from Microsoft. We are thinking of going down this path to replace our aging computer suites at the school that I work. Should be good.

The T150 has 2 x PS/2 ports – keyboard and mouse. 3 x USB ports – 2 USB for devices and 1 USB port to connect directly to the MultiPoint server. Headphone and mic jacks. VGA display port. DC power connector. 1 x cable lock slot. 1 x security clip slot. 1 x mounting bracket to attach this little device to the back of your monitor. The device is only 11cm x 6.5cm x 3cm in dimensions. So it’s quite small.

My next avenue for investigation is to find a device that has a network port instead of a direct connection via USB.

 
1 Comment

Posted by on September 26, 2011 in MultiPoint Server, Thin Clients

 

The dreaded ‘Unknown Device’ yellow exclamation mark

Have you ever had the problem where you have reinstalled or upgraded to a new OS and found that some of your devices are no longer working?

If you take a look in Device Manager, you may find the dreaded little exclamation marks staring back at you in some kind of arrogant way, smirking thinking that you will never find out what it is? Well, there is an easy solution.

If you right click the offending device and choose properties, then choose the details tab, then choose ‘Hardware ID’s’ from the drop down box, you will be presented with a cryptic code of what the device is.

For example, you may see something similar to this:

PCI\VEN_8086&DEV_3B64&SUBSYS_146D103C&REV_06

All you have to do is fire up Google and start typing in that line up to (and including) DEV_3B64 for example and you will find that there will be heaps of results. Look through some of these and you will find links to driver download sites which will happily banish the yellow exclamation mark. The one that I listed is for the Intel Management Engine Interface.

Tip: in the list of hardwar id’s, the top id is normally the most detailed item describing exactly what the device is. The listing under this first one, will then start to be more generic and eventually ending up at the manufacturer of the device.

 
Leave a comment

Posted by on September 22, 2011 in Windows 7, Windows XP

 

Connect Windows PowerShell to Outlook Live

After you have installed and configured Windows PowerShell and Windows Remote Management (WinRM) on your computer, you have to connect the Windows PowerShell on your local computer to Outlook Live to perform tasks in your Outlook Live organization.

When you open Windows PowerShell on your computer, you’re in the Windows PowerShell session of your local computer. A session is an instance of Windows PowerShell that contains all the commands that are available to you.

The Windows PowerShell session of your local computer, called the client-side session, only has the basic Windows PowerShell commands available to it. By connecting to Outlook Live, you connect to the Outlook Live server environment, called the server-side session, which contains the Outlook Live commands.

Before you begin

Before you connect, make sure you have the correct version of Windows PowerShell and WinRM installed and configured on your computer. For more information, see Install and Configure Windows PowerShell.

Verify the Outlook Live account you will use to connect is authorized to connect using Windows PowerShell. For more information, see Control Users’ Access to Windows Remote Management.

Connect Windows PowerShell on your local computer to Outlook Live

  1. Click Start > All Programs > Accessories > Windows PowerShell > Windows PowerShell.
  2. Run the following command:

$LiveCred = Get-Credential

  1. In the Windows PowerShell Credential Request window that opens, type the Windows Live ID and password of an Outlook Live account. When you are finished, click OK.
  2. Run the following command:

$Session = New-PSSession -ConfigurationName Microsoft.Exchange -ConnectionUri https://ps.outlook.com/powershell/ -Credential $LiveCred -Authentication Basic -AllowRedirection

Note   The AllowRedirection parameter enables Outlook Live organizations all over the world to connect Windows PowerShell to Outlook Live by using the same URL.

  1. Run the following command:

Import-PSSession $Session

A progress indicator appears that shows the importing of Outlook Live commands into the client-side session of your local computer. When this process is complete, you can run Outlook Live commands.

Disconnect Windows PowerShell from Outlook Live

When you’re finished using the Outlook Live server-side session, always disconnect Windows PowerShell from Outlook Live by running the following command:

Remove-PSSession <Outlook Live session variable>

For example, to disconnect from the server-side session that is defined by the $Session variable, run the following command:

Remove-PSSession $Session

Important   If you close the Windows PowerShell window without disconnecting from the server-side session, your connection to Outlook Live will remain open for 15 minutes. Your account can only have three connections to the server-side session at one time.

 
Leave a comment

Posted by on September 21, 2011 in Outlook Live, PowerShell

 

Outlook calendar items disappearing

My current problem I face is that one of our staff is having problems with their Outlook calendar. All of her appointments disappear!

Outlook is running in cached mode (because it is a laptop which she takes home). If I restore her calendar items from backup, then check them in Outlook Web Access, the appointments appear. But as soon as I start Outlook, all the calendar items disappear.

If I restore the items and configure Outlook for non-cached mode, the calendar items stay put.

I have tried to delete the .ost file and recreate the cache copy but still the problem remains. I have also tried the /resetnavpane and /cleanfreebusy switches.

I might have to leave Outlook setup as non-cached mode for the time being until I can figure this out.

Has anyone got a solution to my problem?

 
Leave a comment

Posted by on September 21, 2011 in Exchange 2003, Outlook

 

How to add printers for ALL users in Windows 7

Adding printers for all users in Windows XP was easy. A registry tweek here and there and all users would get the same printers. But of course, Windows 7 changed all that. But I found a solution.

Open an elevated command prompt (right click Command Prompt and choose Run As Administrator)
Type in this command:

rundll32 printui.dll,PrintUIEntry /ga /n{printer queue name} /Y

for example:

rundll32 printui.dll,PrintUIEntry /ga /n\\172.16.1.1\Library /Y

The ‘/Y’ is to make the printer default.
The /ga command is “global add”

If you want to delete the printer, you can use this command:

rundll32 printui.dll,PrintUIEntry /gd /n\\172.16.1.1\Library

The /gd command is “global delete” – can only delete printers created by /ga

Stop and Start the print spooler once completed or reboot.

net stop spooler

net start spooler

 
Leave a comment

Posted by on September 21, 2011 in Printers, Windows 7

 

Can Adobe CS4 Suite be deployed on Windows MultiPoint Server?

Yes it can!

When I first started playing around with Windows MultiPoint Server 2011, I attempted to install the Adobe CS4 Suite onto the server but it failed stating that the install will not work with this version of Windows (or something to that effect).

I thought I would have to give up my idea of using MPS but I stumbled across this solution which works great!

There is a control panel feature called “install application on remote desktop…” which is a wizard you follow. However there is a quicker command line method.

  1. Login to the server as administrator
  2. Open a DOS prompt (Start/run/cmd) and
  3. Type “change user /install”
  4. Install the software from the CD in the usual way

And there you have it. Works every time that I have tested it. Yay!

Additional note: if the install of Adobe CS4 fails with the program not responding, go into the control panel and turn off UAC, reboot and perform the steps again.

 
1 Comment

Posted by on September 21, 2011 in MultiPoint Server

 

Recovering from Windows registry hive corruption, the smart way.

Taken from: http://www.css-networks.com/2010/12/recovering-from-windows-registry-hive-corruption-the-clever-or-smart-way/

I like this trick. Every time I do it, I think about all those people doing repair installs (in-place upgrades).

It works pretty much every time unless the filesystem is really truly screwed, in which case you need a backup, say from the system restore directory (System Volume Information), as per this knowledgebase article (don’t bother with the recovery console though, use your USB to IDE or USB to SATA cable and fix it from your laptop.)

Here are the symptoms. You try to start up your Windows 2000/XP/Vista/Windows 7 computer and you get a message, white text on black background:

Windows could not start because the following file is missing or corrupt: \WINDOWS\SYSTEM32\CONFIG\SYSTEM

or

Windows could not start because the following file is missing or corrupt: \WINDOWS\SYSTEM32\CONFIG\SOFTWARE

Sometimes, the message is cut short, so you might see “\WINDOWS\SYSTEM32\CONFIG\SYS” or similar. Hint: If it’s really cut short, and you can’t see if it’s SOFTWARE or SYSTEM, do the following procedure on both files. Whichever one is identified as having been repaired, well that’s the one that was broken .

Anyway, how to fix it in 2 minutes:

Use your USB to IDE/SATA adapter cable, and connect the broken machine’s hard drive to your laptop, or your spare PC or whatever. You don’t have to use a USB to IDE/SATA adapter cable – if you’re a person at home with another PC you can stick the drive on a spare IDE or SATA channel. You just need to get that hard drive into a working Windows XP computer for a few minutes.

Windows will mount the broken computer’s hard drive as, say E: or F:. Make sure you have your computer set to show hidden files and also system files. To check this, go into My Computer -> Tools -> Folder Options, -> View Tab, and select “Show hidden files”, and make sure “Hide protected operating system files” is not ticked.

First things first, run chkdsk on that drive, after all it is most likely filesystem corruption that has caused the registry to become corrupt in the first place. In My Computer, right-click the broken computer’s drive and choose properties. Go to tools, “Check Now”, put a tick in only the first box (Automatically fix filesystem errors), and click start. Let that finish before continuing.

Here’s where the magic happens. Go to start -> run, and type regedit [enter]. This will launch the registry editor on your computer. In the registry editor, highlight HKEY_LOCAL_MACHINE, and then go to File -> Load Hive. Find the file that is “missing or corrupt” (from your error message earlier), and choose to load that. It will be in E:\(or F:\)Windows\System32\Config, and will be called just SOFTWARE or SYSTEM. Regedit will ask you to name the hive, just type “badpc” (any old garbage will do – it’s only temporary).

Regedit will say “One or more files containing the registry were corrupt and had to be recovered by use of log files. The recovery was successful.” You have just repaired the registry! Now you need to Un-load that hive, so highlight that “badpc” hive that you can now see under HKEY_LOCAL_MACHINE, and go to File -> Unload Hive.

You now just need to put that hard drive back in the broken computer, which hopefully won’t be broken any more! If you used a USB to SATA or USB to IDE cable from your laptop, make sure you use the “Safely remove hardware” icon in the system tray next to the clock to safely remove the hard drive, else you may cause filesystem corruption again. Alternatively just shut your laptop/working computer down properly and remove the hard drive once it’s shut down.

All done.

Some background:

The registry is a database. It has transaction log files which can be used to recover from corruption. It would appear that the early Windows boot process is not able to work with those log files, but regedit (and Windows itself further on in the boot process) is.

 
Leave a comment

Posted by on September 21, 2011 in Registry