Windows NT Backup Restore Utility for Windows 7 restores backups made on Windows XP and Windows Server 2003 to computers that are running Windows 7.
Recent Posts
Showing posts with label Windows. Show all posts
Showing posts with label Windows. Show all posts
"Windows NT Backup Restore Utility" for Windows 7
File Server Capacity Tool helps scale file server sizing
Rick Vanover reminds Windows administrators that Microsoft's new File Server Capacity Tool isn't a storage silver bullet.
Microsoft is offering a new product called the File Server Capacity Tool (FSCT) to provision file servers. The tool originates from its use as a Microsoft internal tool for file servers.
This TechNet blog gives a history of how FSCT became a candidate for a customer product.
FSCT will plan servers using CIFS, SMB, or SMB2 storage protocols. The FSCT product will also offer guidance on performance and the maximum number of users, as well as provide additional counters for monitoring file resources.
FSCT planning elements will work across storage devices and Active Directory-based users in a domain. Figure A shows this communication flow.
Figure A
Note that FSCT doesn't provide any silver bullet related to your storage, as "the storage is the storage". Simply knowing where best to place and provision the storage is where FSCT can aid administrators.
Check out the FSCT forum for the beta and release candidate to see what other admins are going through with the product. It may also be worth exploring the FSCT release candidate, which is available through registration on the Microsoft Connect site (sign in to the site and search for "FSCT").
For more information on FSCT and other storage-related technologies for Windows, keep an eye on Microsoft blogger Jose Barreto's site.
READ MORE - File Server Capacity Tool helps scale file server sizing
Microsoft is offering a new product called the File Server Capacity Tool (FSCT) to provision file servers. The tool originates from its use as a Microsoft internal tool for file servers.
This TechNet blog gives a history of how FSCT became a candidate for a customer product.
FSCT will plan servers using CIFS, SMB, or SMB2 storage protocols. The FSCT product will also offer guidance on performance and the maximum number of users, as well as provide additional counters for monitoring file resources.
FSCT planning elements will work across storage devices and Active Directory-based users in a domain. Figure A shows this communication flow.
Figure A
Note that FSCT doesn't provide any silver bullet related to your storage, as "the storage is the storage". Simply knowing where best to place and provision the storage is where FSCT can aid administrators.
Check out the FSCT forum for the beta and release candidate to see what other admins are going through with the product. It may also be worth exploring the FSCT release candidate, which is available through registration on the Microsoft Connect site (sign in to the site and search for "FSCT").
For more information on FSCT and other storage-related technologies for Windows, keep an eye on Microsoft blogger Jose Barreto's site.
Disabling automatic drive letter assignment
Advanced storage configurations in Windows may require you to disable the automatic drive enumeration. Rick Vanover outlines this advanced configuration area of Windows storage.
For certain situations, it may be necessary to tell Windows not to automatically mount new storage that become visible to the server.
This is most frequently used in systems where Microsoft Clustering Services (MSCS) are used, certain virtualization technologies such as VMware Consolidated Backup, or moving a disk from one operating system to another on a shared storage environment.
In the first scenario, MSCS accommodates for this by having Windows not do this by default. The issue is that only Enterprise and Datacenter editions of Windows offer MSCS.
While you can't run MSCS on Standard editions of Windows Server (2003 and 2008), you can enable this auto enumeration of the volumes as they arrive. For Enterprise or Datacenter editions, you can enable this feature by a reverse set of commands from the example.
To do this, you'll need to use the Windows diskpart command to disable automatic drive enumeration on a Windows Standard edition installation with the following commands:
Figure A
Click the image to enlarge.
This is not a huge change to the storage subsystem, but it is a variant from the default configuration of Windows Server. You should only do this on an as-needed basis and before any shared storage or local storage is attached that isn't backed up yet.
Rick Vanover is a Systems Administrator in Columbus, Ohio. He has more than 12 years of IT experience, and he focuses on virtualization, Windows-based server administration, and system hardware.
READ MORE - Disabling automatic drive letter assignment
For certain situations, it may be necessary to tell Windows not to automatically mount new storage that become visible to the server.
This is most frequently used in systems where Microsoft Clustering Services (MSCS) are used, certain virtualization technologies such as VMware Consolidated Backup, or moving a disk from one operating system to another on a shared storage environment.
In the first scenario, MSCS accommodates for this by having Windows not do this by default. The issue is that only Enterprise and Datacenter editions of Windows offer MSCS.
While you can't run MSCS on Standard editions of Windows Server (2003 and 2008), you can enable this auto enumeration of the volumes as they arrive. For Enterprise or Datacenter editions, you can enable this feature by a reverse set of commands from the example.
To do this, you'll need to use the Windows diskpart command to disable automatic drive enumeration on a Windows Standard edition installation with the following commands:
diskpart automount disable automount scrub exitAt this point, the system will automatically mount the drives as they are discovered on the server. This sequence of commands is shown in Figure A.
Figure A
Click the image to enlarge.
This is not a huge change to the storage subsystem, but it is a variant from the default configuration of Windows Server. You should only do this on an as-needed basis and before any shared storage or local storage is attached that isn't backed up yet.
Rick Vanover is a Systems Administrator in Columbus, Ohio. He has more than 12 years of IT experience, and he focuses on virtualization, Windows-based server administration, and system hardware.
Display a full Windows command-prompt history
By changing the size of this history list, you can all commands you've typed in a particular session and avoid frustration.
If you often work from a Microsoft Windows command prompt, chances are you know that you can cycle through a list of all the commands that you've typed in a particular session using the up and down arrows on your keyboard.
You can also change the size of this history list by clicking the command button in the upper left corner, selecting the Properties command, and then changing the buffer size number on the Options tab under Command History.
By default, the buffer size is set to 50, which means that the command history can potentially contain a lot of commands, making it difficult to cycle through all the commands that you've typed by using the up and down arrows on your keyboard. However, there's an easier way to see all those commands.
At the command prompt, enter the following:
Figure A
A list shows my last few commands have been ping commands
Note: This tip applies to Windows XP Home, Windows XP Professional and Windows Vista.
READ MORE - Display a full Windows command-prompt history
If you often work from a Microsoft Windows command prompt, chances are you know that you can cycle through a list of all the commands that you've typed in a particular session using the up and down arrows on your keyboard.
You can also change the size of this history list by clicking the command button in the upper left corner, selecting the Properties command, and then changing the buffer size number on the Options tab under Command History.
By default, the buffer size is set to 50, which means that the command history can potentially contain a lot of commands, making it difficult to cycle through all the commands that you've typed by using the up and down arrows on your keyboard. However, there's an easier way to see all those commands.
At the command prompt, enter the following:
doskey /historyYou'll see a full listing of all the commands that you've entered in a current session (Figure A).
Figure A
A list shows my last few commands have been ping commands
Note: This tip applies to Windows XP Home, Windows XP Professional and Windows Vista.
Secure Yourself Against Conficker Worm
Windows OS users across the globe have been worried sick about the Conficker worm striking back this April 1.
Anti-virus and security solutions providing companies like Symantec, F-Secure, Avast! and others are however singing a relieved tune. That's because they say they're prepared to tackle it.
What's this Conficker worm anyway?
The 'C' variant of Conficker worm, aka Downadup or Kido, infects Windows machines (XP and Vista) and disables them to get security updates or patches from Microsoft and from other vendors. According to Symantec, the creators of the worm will also start using a communications system that is more difficult for security researchers to interrupt.
(Image source: Wikimedia)
How will Conficker harm users?
While nobody knows what exactly Conficker will actually do, most likely, the worm will be used to create a botnet that will be rented out to criminals who want to send SPAM, steal IDs and direct users to online scams and phishing sites.
What can be done to protect a computer from this worm?
First of all, update your anti-virus software. Especially on April 1, make sure that it's actually running when you start your computer. Secondly, make sure that you have the latest Windows security updates.
You should know:
1. Changing the date of your system will not help avoid this worm.
2. Keeping your computer shut on April 1 will also not help either.
3. The only way to get past this worm is by updating Windows and your anti-virus software.
Conficker History
The 'B' variant of the Conficker worm had created ruckus around January this year. By February, it had affected over 9 million Windows users worldwide. Perturbed by the virus, Microsoft had even announced to pay reward of $250,000 to any individual who'll find out the culprits behind Conficker.
Last words
Before this April 1 -- Don't be a fool, download the security tool.
Wubi: Install Ubuntu in Windows Partition - A Complete Guide
Now you have an easy-to-use tool for installing Ubuntu linux into your PCs without disturbing your Windows installation. One of the latest releases by Ubuntu, Wubi can do it for you. With Wubi you can install or uninstall Ubuntu on Windows. This application will enable installation of Linux on the Windows partitions, and that even in a single folder. That implies you don't need partitioning for installation. Wubi can run as a Windows application. The installation can be accomplished without re-partitioning of the drive and there is no risk for wiping out of existing data. What's more, Wubi is free to download. So let's get on with the installation to make the mutt's nuts out of a dual-OS PC.
Before moving to the installation, I need to get you acquainted checks for using Wubi.
When you are done with the above step, a folder will be created in its place having the necessary partitions as files in it.
When the installation is complete reboot your system. You will find an option for booting into Ubuntu.
Now that you are done with the installation. I have some more things to add for your convenience.
Here are the steps to Uninstall Ubuntu
Once you are over with it Ubuntu will be removed from your computer.
Now if you are enjoying this hack to run Ubuntu on Windows partition using Wubi, let me know if you had any crunches.
READ MORE - Wubi: Install Ubuntu in Windows Partition - A Complete Guide
Before moving to the installation, I need to get you acquainted checks for using Wubi.
Things to check before installation
Certain requirements you need to meet before installation- In order to start with the installation you need to have the Wubi that accompanies the newly released Ubuntu. In case, you don't have that just download the executable file for free.
- If you have a high speed Internet connection you don't need to burn a disc for installation. Use the ISO file instead.
- Ensure that you download the right version of Wubi for Ubuntu installation
- If you are using a disc, make sure it's a standard desktop version of Ubuntu.
- You need to have - 256 MB memmory, 5 GB harddisk space and Windows 98, 2000, XP, Vista.
How to Install Ubuntu in Windows
Follow the steps below for installationStep 1
Download the disc image in the form of an ISO file and copy it into the folder with Wubi executable.Step 2
Double click the Wubi executable. The installer will detect the ISO file and installation starts.Step 3
WIndows will ask you to enter the username and password for the OS. Enter them and remember them as you would need them to enter the distribution.Step 4
When prompted, enter the size that you want to allocate for the distribution on the hard drive. Also choose the location where you want to install the Ubuntu.When you are done with the above step, a folder will be created in its place having the necessary partitions as files in it.
Step 5
Now click on the install to start the installation.When the installation is complete reboot your system. You will find an option for booting into Ubuntu.
Now that you are done with the installation. I have some more things to add for your convenience.
Uninstalling Ubuntu
Later on, if you decide that Ubuntu isn't meant for you, uninstall it. Uninstalling Ubuntu is pretty much same as uninstalling any other Windows application.Here are the steps to Uninstall Ubuntu
Step 1
After booting into Window, click on the Start buttonStep 2
Enter the Control Panel and select the Add/Remove Programs option.Step 3
Click on the Ubuntu and then click on the Change/RemoveStep 4
Click on the UninstallOnce you are over with it Ubuntu will be removed from your computer.
How to access the Ubuntu Partitions from Windows
Suppose you have started with Ubuntu and you require the files that you were working on in Windows.In order to access the files from Windows you would require an application called Explore2fs. Here's what you need to doStep 1
Download the Explore2fsStep 2
Run the application and click on File. Go to the Open Image file.Step 3
Browse to the \Ubuntu\ disks and get the location where you had installed the Ubuntu.Step 4
Choose to display all kinds of files and select the partition you want to load. You will be able to access the files in it.Trouble with Wubi
I need to inform you about certain hitch ups you might face while using Wubi. There are two problemsInability to access the partition in Ubuntu
Once you boot into the partition in which Wubi installs Ubuntu it will not be accessible. In case you need to access the partition with Ubuntu, you should create a small partition. The size of the partition should be enough for the Wubi Ubuntu installation. This can be done with a partitioning tool like gParted . this is a free partitioning tool. In case you are having a new hard drive allot a small partition for Ubuntu when you are doing the partitions for Windows. Alternately, you can do it by manually mounting the partition in Ubuntu.Fragmentation of virtual disk files
The way Ubuntu is stored on the system is not cool. With use you'll see the large virtual disk files getting fragmented. So if you don't want the Linux to go slow defrag once in a while.Now if you are enjoying this hack to run Ubuntu on Windows partition using Wubi, let me know if you had any crunches.