Microsoft Press is offering an eBook with selected chapters from the Windows 7 Resource Kit for free. The topics discussed are “deployment platforms, planning, testing application compatibility and more.”
Yearly Archive for 2009
Page 2 of 3
Verizon’s anti-iPhone gets its first commercial: ‘Droid Does’. I guess this means that Verizon has no interest in getting the iPhone on its network despite all the rumors.
Native boot from VHD on a Windows XP computer. I figured it would be a matter of time before someone found a way to make this possible. And now it is.
While we were installing SQL 2008 on our Server 2008 cluster, we received the following error during the validation steps:
Failed at Validate SCSI-3 Persistent Reservation
After searching around, I came across a few posts which led me to this pdf from HP – Implementing Microsoft Windows Server 2008 on HP ProLiant servers. On page 17, it states the following:
Configuring EVA host connections
Make sure the Windows LH Host mode is enabled for each node on the Enterprise Virtual Array (EVA) through command view. Depending on what command view you have installed, if in the drop-down there is no “Microsoft Windows LH” then choose custom and type in the custom type field the following HEX number 00000004198009A8 (Figure 1). If the wrong connection type is configured, you cannot share the disks between the cluster nodes and the cluster check will fail with a non-SCSI-3 compliant message.
The image below, taken from that document, shows where to enter that value if you aren’t familiar with Command View.
Since we had an EVA with a slightly older firmware, we selected the custom field, entered the value in, and everything installed successfully.
Brand new Exchange 2010 Virtual Labs. They have one on transitioning from Exchange 2007 to 2010.
T-Mobile, Danger lose Sidekick customer data due to server failure. Rumor on the street is that a SAN upgrade gone awry caused the data loss. And it seems that there were no backups of the data. (via TechCrunch)
Exchange Server 2007 won’t run on next Windows Server. This includes Server 2008 R2. I wonder how many customers are going to be thrilled with this news.
It seems that Outlook 2010 will have support for multiple exchange mailboxes. After reading through some of the post comments, it does look like it will have support for caching on the extra accounts and that the max number of exchange accounts as of now is 3. That number may change by the time it hits the shelves.
I did have a couple of questions though.
1) Is Exchange 2007 going to support this? As of now, I don’t see how you can attach another mailbox to an existing user with a mailbox. Unless a future service pack will address this issue, I have a feeling only the next version of Exchange will support this. Please correct me if I am wrong.
2) How are Windows Mobile phones going to handle multiple mailboxes?
These questions have been asked in the comments, but they haven’t addressed them yet.
Considerations when hosting Active Directory domain controller in virtual hosting environments. Some of these may seem obvious, but it’s still worth reading.
A few weeks ago, we had a user complain that they were not able to access anything on the network. If I recall correctly, she was able to log in to the domain, but that was pretty much it. She wasn’t able to access any of the resources on the network.
After we started researching the problem, we found a few entries that pointed to a virus being the cause of the issue. We couldn’t find any traces of a virus after running multiple scans.
Next on the list was to rebuild the TCP/IP stack. If you don’t know how to rebuild a TCP/IP stack, you can follow the instructions on Knowledge Base article 299357. Essentially, you have to run one command from the command prompt:
netsh int ip reset filename.txt
After a quick reboot, the issue was still there.
After we researched some more, I came across a post that stated we needed to check a value for a key inside the registry. The key was located at:
HKLM\SYSTEM\CurrentControlSet\Services\NetBT\Parameters\TransportBindName
The value is supposed to be “\Device\” (see image above) without the quotations. We added that value, restarted the machine, and everything was back to normal.
Elsewhere