Anyone who has used Virtual PC / Virtual Server for a while will have got their head around the fact that you cannot access physical hardware directly from the virtual machine - with the exception of devices connected to a serial or parallel port. Well, as a number of people have discovered there is an interesting exception for 'internal modems'. These are modems that are usually on a PCI card in the physical computer - or on a PCMCIA card in a laptop. The trick here as that internal modems almost always implement a hidden serial port - to which the modem is hardwired. This is true even of WinModems. As such - all you need to do is to figure out which COM port is used by the internal modem (poking around under Device Manager will usually get you the answer quickly) and map that to COM1 in the virtual machine. You can then just use a 'generic modem' configuration in the virtual machine to get this to work. Source: http://blogs.msdn.com/virtual_pc_guy |
|
|
Windows XP and Windows Server 2003 contain the WMI (Windows Management Instrumentation) Wmic.exe command-line utility. By using Wmic.exe we can get a lot of information about computer (server).
To display the local computer name and serial number of Main Board I’ve created a very simple script, SerNum.bat. SerNum.bat contains: @echo off
Setlocal
For /F %%a in ('wmic baseboard GET SerialNumber /value^|find "SerialNumber"') do Set %%a
@echo %Computername% - %SerialNumber%
endlocal
On my desktop, the above script displays:
PELEKAN-XP1 - VF0SA75A0SK |
| | Read more... |
The Forefront server security products provide several key security capabilities to Exchange and SharePointcustomers, including an advanced multiple anti-virus engine manager that allows you to concurrently run up to 5 of the included Microsoft and third-party anti-malware engines. Using multiple scan engines delivers several critical advantages: - It increases the chances that emerging threats will be quickly caught.
- It provides redundancy to help protect against scan failures or defects in individual engines; if an engine fails, other engines continue scanning messages.
- It gives administrators an effective way to choose the most appropriate level of protection for their environment given their security needs and server performance capabilities.
- It allows engines to be taken offline for updates or reconfiguration without forcing messages to be queued.
A recent set of tests performed by the independent AV-Test.org group found some surprising differences in signature update times from various vendors. The tests compared AV lab response times for eighty-two “in the wild” viruses and variants. Twenty-six of the viruses were quickly detected by all the scan engines, but some engines didn’t detect viruses for more than twenty-four hours. In a few cases (notably 0506 Banwarum.C@mm), some vendors didn’t update their signatures to provide a block until nearly five days had elapsed! Because Forefront Security for Exchange Server and Forefront Security for SharePoint combine multiple engines, the odds that a virus will go unblocked or undetected for long periods are greatly reduced. Organizations benefit from all updates for the set of engines you use, not just from updates to a single engine. check out the chart at source. For a larger version of this chart go here |
|
The first step is to create a registry file, let say the name of file will be Owner.reg: Double-click your Owner.reg file to apply it to the registry. You will have to grant access, click Continue.
The registry editor will give you a security prompt, click Yes.
You will be greeted with the following message from the registry editor, click Ok: When you hold shift and right-click on a file or folder you will have the option of changing the ownership. Please note that before the ownership will be changed, you must grant access, click Continue.
In order to verify that the “Take Ownership" dialog successfully processed, you can right-click on a file, choose Properties and then choose Details and you will see the “Owner” section changed to COMPUTERNAME\USERNAME. |
|
FileMenu Tools lets customize the context menu of the Windows Explorer. It lets configure the following aspects:
* Add some build-in utilities in order to do operations over files and folders.
* Add customized commands which let run external applications, copy/move to a specific folder or delete specific file types.
* Configure the "Send to..." submenu.
* Enable/disable the commands which are added by other applications to the context menu. |
| | Read more... |
|
|
|
|
| Page 10 of 16 |
Tips & Tricks
