Just a bit of IT humour.
I was trying to perform some operation and I got this message from the server.
Computer is UNWILLING :-)
Sounds like it can perform the request, it just does not want to :-D
Something like "Computer says no" literally
Thursday, 3 December 2009
Computer literally says no :-)
Hi,
Just a bit of IT humour.
I was trying to perform some operation and I got this message from the server.
Computer is UNWILLING :-)
Sounds like it can perform the request, it just does not want to :-D
Something like "Computer says no" literally
Just a bit of IT humour.
I was trying to perform some operation and I got this message from the server.
Computer is UNWILLING :-)
Sounds like it can perform the request, it just does not want to :-D
Something like "Computer says no" literally
Exchange 2010 PrepareSchema error.
Hi,
Just want to share some of my experience installing Exchange 2010.
I was preparing the domain for Exchange 2010 and was trying to run the schema update (setup /PrepareSchema). But every time I was trying to run it I was getting the following error
Copying Setup Files . 5%
An error occured while copying file D:\\Setup\ServerRoles\Common\LPSetupUI.exe.
The error code was 5.
Search in Google did not give any information about this particular problem, so I was trying different possible solutions (replace source, check if all prerequisites are installed, etc). Eventually the solution came very easy. When I was getting the error I was trying to perform setup /PrepareSchema from the terminal session started as the console (mstsc -console), but when I started the same procedure from the actual console (from the keyboard on the server) it worked perfectly.
So here is the small tip, do not run schema preparation from the terminal session.
I was preparing the domain for Exchange 2010 and was trying to run the schema update (setup /PrepareSchema). But every time I was trying to run it I was getting the following error
Copying Setup Files . 5%
An error occured while copying file D:\\Setup\ServerRoles\Common\LPSetupUI.exe.
The error code was 5.
Search in Google did not give any information about this particular problem, so I was trying different possible solutions (replace source, check if all prerequisites are installed, etc). Eventually the solution came very easy. When I was getting the error I was trying to perform setup /PrepareSchema from the terminal session started as the console (mstsc -console), but when I started the same procedure from the actual console (from the keyboard on the server) it worked perfectly.
So here is the small tip, do not run schema preparation from the terminal session.
Thursday, 26 November 2009
Windows 7 the N and E version
Hi everybody,
Just want to share a small interesting thing about Windows 7. Few days ago I bought a new laptop with Windows 7 Home Premium N. I was wondering what “N” stands for, but did not have a chance to Google and read the explanation.
So, I installed all applications which I needed, including recent video codecs and Windows Media Player Classic. After that I have tried to run some *.wmv files, but the Windows Media Player Classic was saying “Cannot render…” I have tried to download and install more codecs, but it still was not working. After several tries I wanted to open the WMV files using Windows Media Player, but I could not find it on the system! And here comes the time for the “N” in the end of the operating system’s name. It turns out that “N” means that Windows Media Player is not included in this release of Windows 7 (because of the European Antimonopoly law) and you have to download it from the Microsoft website.
So, if you have version of Windows 7 with “N” in the end, you have to install the Windows Media Player manually.You can download all the required features from here
Regarding the Windows 7 E version. Those of you who read my article about the Internet Explorer in Windows 7, should remember that OEM version of Windows 7 will be delivered with no internet browser in Europe. So just for your information, this version is called Windows 7 E, and if you bought it, please do not panic when you cannot find Internet Explorer on your PC after you installed Windows 7 E :- )
Thanks,
Kudrat
Just want to share a small interesting thing about Windows 7. Few days ago I bought a new laptop with Windows 7 Home Premium N. I was wondering what “N” stands for, but did not have a chance to Google and read the explanation.
So, I installed all applications which I needed, including recent video codecs and Windows Media Player Classic. After that I have tried to run some *.wmv files, but the Windows Media Player Classic was saying “Cannot render…” I have tried to download and install more codecs, but it still was not working. After several tries I wanted to open the WMV files using Windows Media Player, but I could not find it on the system! And here comes the time for the “N” in the end of the operating system’s name. It turns out that “N” means that Windows Media Player is not included in this release of Windows 7 (because of the European Antimonopoly law) and you have to download it from the Microsoft website.
So, if you have version of Windows 7 with “N” in the end, you have to install the Windows Media Player manually.You can download all the required features from here
Regarding the Windows 7 E version. Those of you who read my article about the Internet Explorer in Windows 7, should remember that OEM version of Windows 7 will be delivered with no internet browser in Europe. So just for your information, this version is called Windows 7 E, and if you bought it, please do not panic when you cannot find Internet Explorer on your PC after you installed Windows 7 E :- )
Thanks,
Kudrat
Thursday, 15 October 2009
Office 2007 Ultimate and Windows 7 Home Premium, special offer for the UK students
Hi,
Today I have received a TechNet Newsletter from Microsoft UK and here is the good news for students. If you have a valid e-mail address ending with ac.uk you are eligible for a special offer on Office 2007 Ultimate and Windows 7 Home Premium. Ready to hear the prices? :-) Office 2007 Ultimate is £38.95 and Windows 7 Home Premium is £30. Believe me this is a bargain, these prices are several times cheaper than a standard price. So if you where planning to buy one of these packages, you can save some money for Christmas party :-)
Cheers,
Kudrat
Today I have received a TechNet Newsletter from Microsoft UK and here is the good news for students. If you have a valid e-mail address ending with ac.uk you are eligible for a special offer on Office 2007 Ultimate and Windows 7 Home Premium. Ready to hear the prices? :-) Office 2007 Ultimate is £38.95 and Windows 7 Home Premium is £30. Believe me this is a bargain, these prices are several times cheaper than a standard price. So if you where planning to buy one of these packages, you can save some money for Christmas party :-)
Cheers,
Kudrat
Tuesday, 29 September 2009
ESX 4.0.0 build-164009 and HP ProLiant DL380 G6
Hello people,
Thanks,
Kudrat
Here is a quick one. Yesterday I installed VSphere ESX 4.0 build-164009 on the HP ProLiant DL380 G6 server. After installing ESX I tried to install Windows 2008 Standard R2 x64 as a guest machine, but the installation could not see the hard drives. As usual I tried to download RAID controller drivers and point the installation to those drivers, but still no luck. I tried different drivers, no luck. Then I tried different OS (W2003R2STD x64) with different drivers, nothing has happened the installation could not see the hard drives. I spent few hours trying different systems and drivers, I even updated ROM on the server with some updates specific for ESX 4.0, but nothing helped.
Eventually, after several hours of the useless efforts, ESX 4.0 was updated to build-175625 using vCenter Update Manager, and guess what, everything started working!!! After that I tried to install ESX 4.0 build-171294, just to check how it will work on the same server, and it worked perfectly, the Windows 2008 STD R2 x64 installation saw the hard drives and ran with no problems.
So, I can only assume that ESX 4.0 build-164009 has some hardware incompatibility with HP ProLiant DL380 G6 server. I did not test this build on the other servers and cannot say if it is happening with other hardware, but if you are having problems using ESX 4.0.0 build-164009 and HP ProLiant DL380 G6, just update your ESX 4.0 to a higher build.
Eventually, after several hours of the useless efforts, ESX 4.0 was updated to build-175625 using vCenter Update Manager, and guess what, everything started working!!! After that I tried to install ESX 4.0 build-171294, just to check how it will work on the same server, and it worked perfectly, the Windows 2008 STD R2 x64 installation saw the hard drives and ran with no problems.
So, I can only assume that ESX 4.0 build-164009 has some hardware incompatibility with HP ProLiant DL380 G6 server. I did not test this build on the other servers and cannot say if it is happening with other hardware, but if you are having problems using ESX 4.0.0 build-164009 and HP ProLiant DL380 G6, just update your ESX 4.0 to a higher build.
Thanks,
Kudrat
Monday, 28 September 2009
Filtering Group Policy from Applying (Windows Server 2003)
Hi,
Here is a small post about filtering a Group Policy from applying to some users. I have recently met several engineers confused by the Group Policies applied to the Terminal Services.
Here is the scenario:
- You create an OU for your Terminal Server
- You put your Terminal Server into that OU
- You create and apply a Group Policy with enabled Loopback processing which applies some restrictions, for example disables RUN or disables access to the local hard drives, etc.
- You try to logon to the Terminal Server as an Administrator and cannot perform your administrative task, because you do not have the RUN and do not have an access to the local hard drives.
Some engineers are trying to create a separate OU with a GPO which has no restrictions and they set Block Policy Inheritance on that OU, thus they are hoping that the Administrator will not have any restrictions on the Terminal Server. But they are forgetting the golden rule of the Loopback Processing, as we remember Group Policy Loopback Processing is replacing all User Configuration settings, which means that the Administrator will still be getting all User Settings from the GPO applied to the OU with your Terminal Server.
If you do not want a GPO from the Terminal Server to be applied to the Administrator’s account here is a simple and easy solution.
1) Open the Properties page of your Terminal Server OU and go to the Group Policy tab.
2) In the Group Policy tab click on the Properties button and in the new windows go to Security tab. In the Security tab pick (add if not shown) required Group or User, for example Administrator and tick Deny in front of Apply Group Policy.
By doing this we have filtered the Group Policy from applying to the Administrator’s account.
You see, it was easy :-)
Take care,
Kudrat
Here is the scenario:
- You create an OU for your Terminal Server
- You put your Terminal Server into that OU
- You create and apply a Group Policy with enabled Loopback processing which applies some restrictions, for example disables RUN or disables access to the local hard drives, etc.
- You try to logon to the Terminal Server as an Administrator and cannot perform your administrative task, because you do not have the RUN and do not have an access to the local hard drives.
Some engineers are trying to create a separate OU with a GPO which has no restrictions and they set Block Policy Inheritance on that OU, thus they are hoping that the Administrator will not have any restrictions on the Terminal Server. But they are forgetting the golden rule of the Loopback Processing, as we remember Group Policy Loopback Processing is replacing all User Configuration settings, which means that the Administrator will still be getting all User Settings from the GPO applied to the OU with your Terminal Server.
If you do not want a GPO from the Terminal Server to be applied to the Administrator’s account here is a simple and easy solution.
1) Open the Properties page of your Terminal Server OU and go to the Group Policy tab.
2) In the Group Policy tab click on the Properties button and in the new windows go to Security tab. In the Security tab pick (add if not shown) required Group or User, for example Administrator and tick Deny in front of Apply Group Policy.
By doing this we have filtered the Group Policy from applying to the Administrator’s account.
You see, it was easy :-)
Take care,
Kudrat
Friday, 14 August 2009
Disable BEEPS during the terminal session.
Hi everybody,
Yesterday, I had a complaint from a client about a weird sound coming out of the computer during a terminal session. I was a bit surprised as the sound redirection was disabled by the group policy. I have connected to that Terminal Server and found out that it was the BEEP service sound. For example when you receive an e-mail, Outlook tries to notify you, but as the sound was turned off, you get a beep notification.
There are few workarounds for this, I would say, inconvenience.
1) The simplest one is stopping the BEEP service on the client’s local machine.
If you issue the following command in the command prompt:
net stop beep
this will stop the BEEP service on the local machine, but after restart the BEEP service will start again. So if you want to get rid of these beeps forever you have to disable the BEEP service by issuing the following command:
sc config beep start= disabled
This will stop the BEEP service from starting automatically.
2) The second solution is to disable BEEP on the server, so that no signal is sent to the Terminal Services client. To do this you have to perform following:
- Open the Registry editor by issuing regedit command
- In the registry editor find the following subkey KEY_LOCAL_MACHINE\System\CurrentControlSet\Control\Terminal Server
- In this subkey create a new DWORD value and name it DisableBeep
- Modify the DisableBeep key and put 1 in the Value Data box.
As you have already understood by entering 1 you are turning on the DisableBeep key, in the future if you decide to turn on (i.e turn off the DisableBeep key) the BEEPservice on the server all you have to do is to enter 0 instead of 1 in the Value Data box for the DisableBeep DWORD key.
The only disadvantage of the second option is that you have to restart the Terminal Server, which sometimes can be a very difficult task as loads of user accessing it 24 hours a day :-)
Take care,
Kudrat
Yesterday, I had a complaint from a client about a weird sound coming out of the computer during a terminal session. I was a bit surprised as the sound redirection was disabled by the group policy. I have connected to that Terminal Server and found out that it was the BEEP service sound. For example when you receive an e-mail, Outlook tries to notify you, but as the sound was turned off, you get a beep notification.
There are few workarounds for this, I would say, inconvenience.
1) The simplest one is stopping the BEEP service on the client’s local machine.
If you issue the following command in the command prompt:
net stop beep
this will stop the BEEP service on the local machine, but after restart the BEEP service will start again. So if you want to get rid of these beeps forever you have to disable the BEEP service by issuing the following command:
sc config beep start= disabled
This will stop the BEEP service from starting automatically.
2) The second solution is to disable BEEP on the server, so that no signal is sent to the Terminal Services client. To do this you have to perform following:
- Open the Registry editor by issuing regedit command
- In the registry editor find the following subkey KEY_LOCAL_MACHINE\System\CurrentControlSet\Control\Terminal Server
- In this subkey create a new DWORD value and name it DisableBeep
- Modify the DisableBeep key and put 1 in the Value Data box.
As you have already understood by entering 1 you are turning on the DisableBeep key, in the future if you decide to turn on (i.e turn off the DisableBeep key) the BEEPservice on the server all you have to do is to enter 0 instead of 1 in the Value Data box for the DisableBeep DWORD key.
The only disadvantage of the second option is that you have to restart the Terminal Server, which sometimes can be a very difficult task as loads of user accessing it 24 hours a day :-)
Take care,
Kudrat
Subscribe to:
Posts (Atom)
