Network Administration & Consulting Services

• Comment out the line “:::1    localhost”
• Add the following two lines:

If you are working with BES (BlackBerry Enterprise Server) you can get a problem, when users cannot send emails from their Blackberry. And, I guess you already familiar with a “Send As Permission” problem :).

So, I created a script, that allows set all neccesasry right to the BESADMIN account. When you run script, you should provide an OU, where the particular user exist and user’s email address.

NOTE: In my script I used linex.exe and dsacls.exe. Just use Google to download those very POWERFUL tools

Just recieved anonce about this and here it is:

"Today, Microsoft reaches a significant milestone for customers and partners with the release of Windows Server 2008 Hyper-V, the hypervisor-based virtualization feature included in select versions of Windows Server 2008. Those who have already deployed the x64 versions of Windows Server 2008 can receive Hyper-V from Windows Update beginning July 8, while new customers and partners can download Hyper-V later today (12:00 pm PT). The Windows Virtualization team will be counting down the days to download from Windows Update, so be sure to visit the Windows Virtualization Team blog to see daily spotlights on specific features and benefits of Hyper-V technology, as well as to read about customer stories and see postings from guests.

Since the beta release of Hyper-V in February, more than 250 customers have participated in Hyper-V’s early adoption program. Microsoft’s own deployment and results with Hyper-V is showcased today in Rob Emanuel’s guest blog and video on the Windows Server Division blog, specifically on customers using Hyper-V and partner benefits, visit the Microsoft PressPass site."

Few days ago Microsoft released a Microsoft Virtual PC 2007 with SP1. This update for Microsoft Virtual PC 2007 includes support for the following additional Host and Guest Operating Systems:

Additonal Guest Operating System support:
Windows Vista® Ultimate Edition with Service Pack 1 (SP1)
Windows Vista® Business Edition with Service Pack 1 (SP1)
Windows Vista® Enterprise Edition with Service Pack 1 (SP1)
Windows Server® 2008 Standard
Windows XP Professional with Service Pack 3


Additional Host Operating System support:
Windows Vista® Ultimate Edition with Service Pack 1 (SP1)
Windows Vista® Business Edition with Service Pack 1 (SP1)
Windows Vista® Enterprise Edition with Service Pack 1 (SP1)
Windows XP Professional with Service Pack 3

Download from here

iSCSI has become a very popular way of having shared storage among several physical or virtual computers. The benefits of shared storage are even greater when combined with the abilities of VMWare such as VMotion, High Availability and Distributed Resource Scheduler.

Below are the basic (and I do emphasize basic) to configuring iSCSI storage with VMWare 3.0. Like any shared storage infrastructure there are a number of possible methods and structures that could change the way that iSCSI is installed and used.

Step 1 - Add in extra Service Console and iSCSI VMKernal
The service console and VMKernal need to be on the same physical NIC on the ESX server. The IP’s for these services need to be on the same subnet as the iSCSI storage device. The pictures below outline the end-result if your iSCSI VLAN were to be 192.168.4.0/24. Note that the service console that you is shown below is the second and therefore additional service console. The original stays unchanged.

So I build a new Windows XP ISO with SP3 integrated, this is a Volume License editions (VOL) which only accepts Volume License Keys (VLK). When I want to install it on a clean machine, I noticed that setup prompts for a product key and it does not allow me to continue, which should be a new feature in XP sp3. OK so I fill in the VLK but it does not accept it, I try another one from a customer of mine, does not work either.

I found out that the problem is when you do the XP Sp3 slipstream process on a WIndows Vista machine, the API gives a different response and screws up the PID process. This is a bug and Microsoft knew about this in December, still the bug remained and made it all the way to RTM, nice work Microsoft.

So XP SP slipstream only on XP or 2003 machines!!!

See the dicussion thread here: Key not working after SlipStream 

Source: Bink.nu

By running Oclist on Windows 2008 Server Core we can get full information what Installed and what Not installed on server.
The full list is very long and not comfortable for reading. If you don’t want to include all of the many “Not Installed” options in the output of Oclist, run: