-->![Curio pro 13 2012 specs Curio pro 13 2012 specs](https://dynamic-media-cdn.tripadvisor.com/media/photo-o/10/f8/59/ee/photo5jpg.jpg?w=600&h=300&s=1)
![Curio pro 13 2012 model Curio pro 13 2012 model](https://insmac.org/uploads/posts/2017-08/1502647124_curio.png)
What can Curio do for you? In Curio, create a project to represent a real-world project that you’re working on. Next fill it with everything related to that project including notes, images, PDF’s, documents, web links, multimedia, and much, much more. You can place this information anywhere on Curio’s freeform idea spaces. Or use Curio’s integrated mind maps, lists, tables. HALL Arts Hotel Dallas, Curio Collection by Hilton, Texas, USA Earn Now & Travel Later Apply for the Hilton Honors AMEX Card and you can earn a one-time $100 statement credit after your first purchase on the Card within the first 3 months, plus earn 75K Points after you spend $1,000 in purchases on the Card in the first 3 months. This MacBook Pro 13' Unibody (Mid 2009-Mid 2012) replacement battery fix kit includes all the parts and tools you need to bring your dead MacBook Pro back to life! 100% factory tested. Spot tested by iFixit staff in San Luis Obispo, CA to ensure consistency of quality and capacity. Assembled using high quality chipset from Texas Instruments.
Applies To: Windows Server 2012, Windows Server 2012 R2
Windows Server Migration Tools Installation, Access, and Removal describes how to locate, install, use, and remove Windows Server Migration Tools. Administrators can use Windows Server Migration Tools to migrate server roles, features, operating system settings, and other data and shares to computers that are running Windows Server® 2012 R2 or Windows Server® 2012.
![Curio pro 13 2012 specs Curio pro 13 2012 specs](https://dynamic-media-cdn.tripadvisor.com/media/photo-o/10/f8/59/ee/photo5jpg.jpg?w=600&h=300&s=1)
This topic supports migrations in which the migration destination servers are running Windows Server 2012 R2 or Windows Server 2012. For information about how to prepare to use Windows Server Migration Tools for migrations to servers that are running Windows Server 2008 R2, see Windows Server Migration Tools Installation, Access, and Removal.
Windows Server Migration Tools installation and preparation can be divided into the following stages.
- Installing Windows Server Migration Tools on destination servers that run Windows Server 2012 R2 or Windows Server 2012.
- Creating deployment folders on migration destination servers, for copying to source servers.
- Copying deployment folders from destination servers to source servers.
- Registering Windows Server Migration Tools on source servers.
In this guide
Supported operating systems
The following table indicates the Windows Server operating systems that Windows Server Migration Tools supports.
Source server processor | Source server operating system | Destination server operating system | Destination server processor |
---|---|---|---|
x86- or x64-based | Windows Server 2003 with Service Pack 2 | Windows Server 2012 R2 or Windows Server 2012, both full and Server Core installation options | x64-based |
x86- or x64-based | Windows Server 2003 R2 | Windows Server 2012 R2 or Windows Server 2012, both full and Server Core installation options | x64-based |
x86- or x64-based | Windows Server 2008, full installation option | Windows Server 2012 R2 or Windows Server 2012, both full and Server Core installation options | x64-based |
x64-based | Windows Server 2008 R2 | Windows Server 2012 R2 or Windows Server 2012, both full and Server Core installation options | x64-based |
x64-based | Server Core installation option of Windows Server 2008 R2 | Windows Server 2012 R2 or Windows Server 2012, both full and Server Core installation options | x64-based |
x64-based | Windows Server 2012 | Windows Server 2012 R2 or Windows Server 2012, both full and Server Core installation options | x64-based |
x64-based | Server Core installation option of Windows Server 2012 | Windows Server 2012 R2 or Windows Server 2012, both full and Server Core installation options | x64-based |
x64-based | Windows Server 2012 R2 | Windows Server 2012 R2, both full and Server Core installation options | x64-based |
x64-based | Server Core installation option of Windows Server 2012 R2 | Windows Server 2012 R2, both full and Server Core installation options | x64-based |
The versions of operating systems shown in the previous table are the oldest combinations of operating systems and service packs that are supported. If available, newer service packs are supported.
Curio Pro 13 2012 Specs
Migrations between physical operating systems and virtual operating systems are supported. Migrations that use Windows Server Migration Tools to migrate to Windows Server 2012 or Windows Server 2012 R2 support cross-subnet migrations.
Migration from a source server to a destination server that is running an operating system in a different system UI language (that is, the installed language) than the source server is not supported. For example, you cannot use Windows Server Migration Tools to migrate roles, operating system settings, data, or shares from a computer that is running Windows Server 2008 in the French system UI language to a computer that is running Windows Server 2012 in the German system UI language.
Note
The system UI language is the language of the localized installation package that was used to set up the Windows operating system.
Both x86- and x64-based migrations are supported for Windows Server 2003 and Windows Server 2008. All editions of Windows Server 2012 R2, Windows Server 2012, and Windows Server 2008 R2 are x64-based.
Roles that are running on the Server Core installation option of Windows Server 2008 cannot be migrated, because the Microsoft .NET Framework is not available in the Server Core installation option of Windows Server 2008.
Permission requirements
At minimum, you must be a member of the Administrators group on both source and destination servers to install, remove, or set up Windows Server Migration Tools.
Prepare for installation
Follow the steps in this section if you are registering Windows Server Migration Tools on migration source servers that are running Windows Server 2003, Windows Server 2008, Windows Server 2008 R2, or Windows Server 2012, and if the source server is running an older release of Windows Server than the migration destination server. For example, if the source server is running Windows Server 2012, but the destination server is running Windows Server 2012 R2. Otherwise, see Install Windows Server Migration Tools.
Note
All commands in this guide are case-insensitive unless specifically noted.
Windows Server 2012 source server
Complete the following tasks to prepare a source server that is running Windows Server 2012 for migration in which the destination server is running Windows Server 2012 R2.
- Verify that the source server has sufficient disk space (at least 23 MB) to store the Windows Server Migration Tools deployment folder.
Windows Server 2008 R2 source server
Complete the following tasks to prepare a source server that is running Windows Server 2008 R2 for Windows Server Migration Tools.
- Verify that the source server has sufficient disk space (at least 23 MB) to store the Windows Server Migration Tools deployment folder.
Windows Server 2008 source server
Complete the following tasks to prepare a source server that is running Windows Server 2008 for Windows Server Migration Tools.
- Verify that the source server has sufficient disk space (at least 23 MB) to store the Windows Server Migration Tools deployment folder.
- Install Windows PowerShell by using Server Manager or by running the Server Manager command prompt tool, ServerManagerCmd.exe. For more information about how to add features to the server by using ServerManagerCmd.exe, see Overview of Server Manager Commands in the Windows Server 2008 Server Manager Help.
Windows Server 2003 or Windows Server 2003 R2 source server
Complete the following tasks to prepare a source server that is running Windows Server 2003 or Windows Server 2003 R2 for Windows Server Migration Tools.
- Verify that the source server has sufficient disk space (at least 25 MB) to store the Windows Server Migration Tools deployment folder.
- Download and install Microsoft .NET Framework 2.0. Microsoft .NET Framework 2.0 is available for download from the Microsoft Web site.
- Download and install Windows PowerShell 1.0, or a later version. Windows PowerShell 1.0 is available for download from the Microsoft Web site.
Note
Windows PowerShell 2.0 and 3.0 are available in a graphically-oriented version, Windows PowerShell ISE. For more information about Windows PowerShell ISE, see Windows PowerShell 3.0 Integrated Scripting Environment (ISE).
Other computers in your enterprise
Because you might have to restart the server after you install Windows Server Migration Tools, notify users in advance that they might experience downtime while the server operating system loads. To minimize downtime, and reduce its effect on users in your enterprise, install Windows Server Migration Tools during off-peak hours.
Install Windows Server Migration Tools
This section describes how to install Windows Server Migration Tools on both source and destination servers. If both source and destination computers are running the same operating system on which Windows Server Migration Tools is available for installation (if both servers are running Windows Server 2012 R2, or both servers are running Windows Server 2012), install Windows Server Migration Tools on both computers by following installation steps in either Full installation option of Windows Server 2012 R2 or Windows Server 2012 or Server Core installation option of Windows Server 2012 R2 or Windows Server 2012.
If you plan to migrate roles, features, or other data from computers that are running older releases of Windows Server than your destination server—that is, Windows Server 2012, Windows Server 2008 R2, Windows Server 2008, or Windows Server 2003—you must complete the following additional tasks after you install Windows Server Migration Tools on destination servers.
- Create a Windows Server Migration Tools deployment folder on destination servers. For more information, see Creating a deployment folder on destination computers.
- Register Windows Server Migration Tools on source computers that are running older releases of Windows Server than your destination server; that is, Windows Server 2012, Windows Server 2008 R2, Windows Server 2008, or Windows Server 2003. For more information, see Registering Windows Server Migration Tools on source computers.
For more detailed information, see Windows Server 2012, Windows Server 2008 R2, Windows Server 2008, or Windows Server 2003 source computers.
Full installation option of Windows Server 2012 R2 or Windows Server 2012
To install Windows Server Migration Tools
- Do one of the following to open a Windows PowerShell session with elevated user rights.NoteIf you are installing Windows Server Migration Tools from a remote server, you do not need to run Windows PowerShell with elevated user rights.
- On the Windows desktop, right-click Windows PowerShell on the taskbar, and then click Run as Administrator.
- On the Windows Start screen, right-click the Windows PowerShell tile, and then on the app bar, click Run as Administrator.
- Type the following, and then press Enter. If you are installing the feature on the local server, omit the ComputerName parameter.NoteYou can also install Windows Server Migration Tools on a full installation of Windows Server 2012 R2 or Windows Server 2012 by using the Add Roles and Features Wizard in Server Manager. For more information about how to use the Add Roles and Features Wizard, see Install or uninstall roles, role services, or features.
Server Core installation option of Windows Server 2012 R2 or Windows Server 2012
Windows PowerShell is installed by default on the Server Core installation option of Windows Server 2012 R2 and Windows Server 2012. By default, programs on the Server Core installation option run as Administrator, so there is no need to start Windows PowerShell with elevated user rights.
To install Windows Server Migration Tools on a Server Core installation of Windows Server 2012
- Open a Windows PowerShell session by typing the following in the current command prompt session, and then press Enter.
- In the Windows PowerShell session, install Windows Server Migration Tools by using the Windows PowerShell Install-WindowsFeature cmdlet for Server Manager. In the Windows PowerShell session, type the following, and then press Enter. Omit the ComputerName parameter if you are installing Windows Server Migration Tools on the local server.
Windows Server 2012, Windows Server 2008 R2, Windows Server 2008, or Windows Server 2003 source computers
Complete the following two tasks to install Windows Server Migration Tools.
- Create deployment folders for source computers by running the smigdeploy.exe tool (included with Windows Server Migration Tools) on your destination server. For more information, see Creating a deployment folder on destination computers.
- Register Windows Server Migration Tools on source computers that are running Windows Server 2012, Windows Server 2008 R2, Windows Server 2008, or Windows Server 2003 by using SmigDeploy.exe. For more information, see Registering Windows Server Migration Tools on source computers.
Creating a deployment folder on destination computers
This procedure describes how to create the deployment folder on your destination server that is running Windows Server Migration Tools. After you create the deployment folder, copy it to the local drive of a migration source server that is running an older release of Windows Server; that is, Windows Server 2012, Windows Server 2008 R2, Windows Server 2008, or Windows Server 2003.
To create a deployment folder on destination computers
- If you have not already installed Windows Server Migration Tools on the destination server, see Install Windows Server Migration Tools in this topic.
- Open a Command Prompt window with elevated user rights. On the Server Core installation option of Windows Server 2012 R2 or Windows Server 2012, an elevated command prompt is already opened by default. On the full installation option, type cmd on the Start screen, right-click the Command Prompt tile, and then click Run as administrator.
- At the command prompt, change to the directory in which the smigdeploy.exe tool is stored. Type the following, and then press Enter.
- Do one of the following to create a Windows Server Migration Tools deployment folder.
- To create a folder to copy to an x64-based computer that is running Windows Server 2012, where Windows Server 2012 R2 is running on the destination server, type the following, in which deployment folder path represents the path of the deployment folder on the source computer, and then press Enter.
- To create a folder to copy to an x64-based computer that is running Windows Server 2008 R2, type the following, in which deployment folder path represents the path of the deployment folder on the source computer, and then press Enter.
- To create a folder to copy to an x64-based source computer that is running Windows Server 2008, type the following, in which deployment folder path represents the path of the deployment folder on the source computer, and then press Enter.
- To create a folder to copy to an x64-based source computer that is running Windows Server 2003, type the following, in which deployment folder path represents the path of the deployment folder on the source computer, and then press Enter.
- To create a folder to copy to an x86-based source computer that is running Windows Server 2008, type the following, in which deployment folder path represents the path of the deployment folder on the source computer, and then press Enter.
- To create a folder to copy to an x86-based source computer that is running Windows Server 2003, type the following, in which deployment folder path represents the path of the deployment folder on the source computer, and then press Enter.
Note
Each of these commands creates a deployment folder named in the format SMT_<Operating System>_<Architecture> and stores it in the specified deployment folder path.
You can also specify a network path as the path for the deployment folder. Verify that you have access to the network path before you create the deployment folder.
For more information about SmigDeploy.exe, at a command prompt, type SmigDeploy.exe /?, and then press Enter.
Registering Windows Server Migration Tools on source computers
Before you can run the Windows Server Migration Tools snap-in for the first time on a source server that is running an older release of Windows Server than your destination server, it must be registered with Windows PowerShell. Use SmigDeploy.exe to register the Windows Server Migration Tools snap-in on a migration source server that is running an older release of Windows Server than your destination server (that is, Windows Server 2012, Windows Server 2008 R2, Windows Server 2008 or Windows Server 2003).
Before you start the procedure in this section, verify the following.
- Microsoft .NET Framework 2.0 is installed on computers that are running Windows Server 2003.
- Windows PowerShell 1.0 or a later version is installed on source computers that are running either Windows Server 2008 or Windows Server 2003. (Windows PowerShell is already installed on computers that are running Windows Server 2008 R2 and Windows Server 2012.)
To register Windows Server Migration Tools
- Copy the Windows Server Migration Tools deployment folder that was created by using the procedure in Creating a deployment folder on destination computers to a local drive on the source computer that is running an older release of Windows Server than your destination server. Be sure that the operating system architecture of the deployment folder matches that of the source computer to which you are copying the folder.For example, the SMT_WS08_amd64 folder should only be copied to the local drive of an AMD64 source computer that is running Windows Server 2008.
- On the source computer, open a Command Prompt window.
- On computers that are running Windows Server 2003 or the Server Core installation option of Windows Server 2008 R2, you do not have to run a Command Prompt window with elevated user rights. Click Start, click Run, type cmd, and then click OK.
- On computers that are running the full installation options of Windows Server 2012, Windows Server 2008 R2 or Windows Server 2008, you must open a Command Prompt window with elevated user rights. To do this, right-click the shortcut for Command Prompt, and then click Run as Administrator.
- At the command prompt, change to the directory to which you copied the Windows Server Migration Tools deployment folder in step 1.NoteYou can register and run Windows Server Migration Tools cmdlets from a removable drive, CD-ROM, or DVD-ROM. However, to increase the reliability of registering the cmdlets, we recommend that you copy the deployment folder to a local drive of the source computer. You cannot register or run Windows Server Migration Tools cmdlets from a network location.
- In the deployment folder directory, type the following command to register Windows Server Migration Tools cmdlets, and then press Enter.
Note
When registration is finished, a status message is displayed that indicates that the registration finished successfully, and a Windows PowerShell session opens. You can run Windows Server Migration Tools cmdlets in this Windows PowerShell session. If you close the Windows PowerShell session, see Windows Server 2003 or Windows Server 2008 source computers for information about how to access and use Windows Server Migration Tools cmdlets.
Use Windows Server Migration Tools
This section describes how to run Windows Server Migration Tools cmdlets.
Full installation option of Windows Server 2012 R2
Start Windows PowerShell and run Windows Server Migration Tools cmdlets by using either of the following procedures. These can apply to either source or destination servers.
To run Windows Server Migration Tools from the Start screen
- To open a Windows Server Migration Tools custom Windows PowerShell session, right-click the Windows Server Migration Tools tile, and then on the app bar, click Run as administrator.
To run Windows Server Migration Tools in a new Windows PowerShell session
- Do one of the following to open a Windows PowerShell session with elevated user rights.
- On the Windows desktop, right-click Windows PowerShell on the taskbar, and then click Run as Administrator.
- On the Windows Start screen, right-click the Windows PowerShell tile, and then on the app bar, click Run as Administrator.
- Load Windows Server Migration Tools into your Windows PowerShell session. Antivirus vk pro 6 1 06. To load Windows Server Migration Tools, type the following, and then press Enter.
Server Core installation option of Windows Server 2012 R2
This procedure applies to either source or destination servers.
To run Windows Server Migration Tools cmdlets
- Type powershell into a command prompt, and then press Enter.
- Load Windows Server Migration Tools into your Windows PowerShell session. To load Windows Server Migration Tools, type the following, and then press Enter.
Full installation option of Windows Server 2012
Start Windows PowerShell and run Windows Server Migration Tools cmdlets by using either of the following procedures. These can apply to either source or destination servers.
To run Windows Server Migration Tools from the Start screen
- To open a Windows Server Migration Tools custom Windows PowerShell session, right-click the Windows Server Migration Tools tile, and then on the app bar, click Run as administrator.
To run Windows Server Migration Tools in a new Windows PowerShell session
- Do one of the following to open a Windows PowerShell session with elevated user rights.
- On the Windows desktop, right-click Windows PowerShell on the taskbar, and then click Run as Administrator.
- On the Windows Start screen, right-click the Windows PowerShell tile, and then on the app bar, click Run as Administrator.
- Load Windows Server Migration Tools into your Windows PowerShell session. To load Windows Server Migration Tools, type the following, and then press Enter.
Server Core installation option of Windows Server 2012
This procedure applies to either source or destination servers.
To run Windows Server Migration Tools cmdlets
- Type powershell into a command prompt, and then press Enter.
- Load Windows Server Migration Tools into your Windows PowerShell session. To load Windows Server Migration Tools, type the following, and then press Enter.
Source computer running full installation option of Windows Server 2008 R2
If you close the Windows PowerShell session that is opened automatically when SmigDeploy.exe finishes registering the Windows Server Migration Tools cmdlets, you can run Windows Server Migration Tools cmdlets by using any of the following procedures.
To run Windows Server Migration Tools from the Start menu
- To open a Windows Server Migration Tools custom Windows PowerShell session, click Start, point to Administrative Tools, open the Windows Server Migration Tools folder, right-click Windows Server Migration Tools, and then click Run as administrator.
To run Windows Server Migration Tools in a new Windows PowerShell session
- Open a Windows PowerShell session with elevated user rights. To do this, click Start, click All Programs, click Accessories, click Windows PowerShell, right-click the Windows PowerShell shortcut, and then click Run as administrator.
- Load Windows Server Migration Tools into your Windows PowerShell session. To load Windows Server Migration Tools, type the following, and then press Enter.
Source computer running Server Core installation option of Windows Server 2008 R2
Start Windows PowerShell and use Windows Server Migration Tools cmdlets by using any of the following procedures.
To open Windows PowerShell together with Windows Server Migration Tools
- At a command prompt on a computer that is running the Server Core installation option of Windows Server 2008 R2, type the following, and then press Enter.
To open Windows PowerShell and load Windows Server Migration Tools separately
- At a command prompt, type the following, and then press Enter.
- Load Windows Server Migration Tools into the Windows PowerShell session. To load Windows Server Migration Tools, type the following, and then press Enter.
Windows Server 2003 or Windows Server 2008 source computers
If you close the Windows PowerShell session that is opened automatically when SmigDeploy.exe finishes registering the Windows Server Migration Tools cmdlets, you can run Windows Server Migration Tools cmdlets by using any of the following procedures.
To open Windows Server Migration Tools from the Start menu
- Do one of the following:
- On computers that are running Windows Server 2003, click Start, point to Administrative Tools, open the Windows Server Migration Tools folder, and then click Windows Server Migration Tools.
- On computers that are running Windows Server 2008, click Start, point to Administrative Tools, open the Windows Server Migration Tools folder, right-click Windows Server Migration Tools, and then click Run as administrator.
To open Windows PowerShell and load Windows Server Migration Tools separately
- Do one of the following:
- On computers that are running Windows Server 2003, open a Windows PowerShell session by clicking Start, clicking All Programs, opening the Windows PowerShell folder, and clicking the Windows PowerShell shortcut.
- On computers that are running Windows Server 2008, open a Windows PowerShell session with elevated user rights. To do this, click Start, click All Programs, open the Windows PowerShell folder, right-click the Windows PowerShell shortcut, and then click Run as administrator.
- In the Windows PowerShell session, type the following to load the Windows Server Migration Tools snap-in, and then press Enter.
To open Windows PowerShell together with Windows Server Migration Tools from a Command Prompt window
- Do one of the following.
- On computers that are running Windows Server 2003, open a Command Prompt window by clicking Start, clicking Run, typing cmd, and then pressing Enter.
- On computers that are running Windows Server 2008, open a Command Prompt window with elevated user rights. To do this, click Start, click All Programs, click Accessories, right-click the Command Prompt shortcut, and then click Run as administrator.
- At the command prompt, change directories to the location of the Windows Server Migration Tools deployment folder.
- In the deployment directory, type the following to open a Windows PowerShell session with preloaded Windows Server Migration Tools cmdlets, and then press Enter.
Additional resources and next steps for using Windows Server Migration Tools
For more information about Windows Server Migration Tools and Windows PowerShell, see the following resources.
- For detailed, step-by-step information about how to migrate specific roles or data, see the Windows Server Migration Portal on the Windows Server TechCenter.
- In a Windows PowerShell session, type the following, and then press Enter to view detailed information about how to use a specific Windows Server Migration Tools cmdlet.
- See the Windows PowerShell page on the Microsoft Web site.
Remove Windows Server Migration Tools
Follow the procedures in this section to remove Windows Server Migration Tools from computers.
Full installation option of Windows Server 2012 R2 or Windows Server 2012
You can use either Server Manager deployment cmdlets, or the Add Roles and Features Wizard in Server Manager to remove Windows Server Migration Tools. If Windows Server 2012 was a source computer for a migration to a server running Windows Server 2012 R2, unregister Windows Server Migration Tools on the source computer instead of uninstalling Windows Server Migration Tools. For more information, see Source computers running full and Server Core installation options of Windows Server 2012.
To uninstall Windows Server Migration Tools from the full installation option
- Do one of the following to open a Windows PowerShell session with elevated user rights.NoteIf you are uninstalling Windows Server Migration Tools from a remote server, you do not need to run Windows PowerShell with elevated user rights.
- On the Windows desktop, right-click Windows PowerShell on the taskbar, and then click Run as Administrator.
- On the Windows Start screen, right-click the Windows PowerShell tile, and then on the app bar, click Run as Administrator.
- Type the following, and then press Enter. If you are uninstalling the feature from the local server, omit the ComputerName parameter.NoteYou can also uninstall Windows Server Migration Tools from a full installation of Windows Server 2012 R2 or Windows Server 2012 by using the Add Roles and Features Wizard in Server Manager. For more information about how to use the Add Roles and Features Wizard, see Install or uninstall roles, role services, or features.
Server Core installation option of Windows Server 2012 R2 or Windows Server 2012
Windows PowerShell is installed by default on the Server Core installation option of Windows Server 2012 R2 or Windows Server 2012. By default, programs on the Server Core installation option run as Administrator, so there is no need to start Windows PowerShell with elevated user rights.
![Curio pro 13 2012 model Curio pro 13 2012 model](https://insmac.org/uploads/posts/2017-08/1502647124_curio.png)
To uninstall Windows Server Migration Tools from the Server Core installation option
- Open a Windows PowerShell session by typing the following in the current command prompt session, and then press Enter.
- In the Windows PowerShell session, uninstall Windows Server Migration Tools by using the Windows PowerShell Uninstall-WindowsFeature cmdlet for Server Manager. In the Windows PowerShell session, type the following, and then press Enter. Omit the ComputerName parameter if you are uninstalling Windows Server Migration Tools from the local server.
Source computers running full and Server Core installation options of Windows Server 2012
To remove Windows Server Migration Tools from a source computer that is running Windows Server 2012, and on which Windows Server Migration Tools was registered for migrating to a destination server running Windows Server 2012 R2, you must first reverse the registration of Windows Server Migration Tools cmdlets, and then remove the deployment folder.
To remove Windows Server Migration Tools from Windows Server 2012
- Do one of the following.
- On computers that are running the full installation option of Windows Server 2012, open a Command Prompt window with elevated user rights. To do this, on the Start screen, type cmd. Right-click the Command Prompt tile, and then click Run as Administrator.
- On computers that are running the Server Core installation option of Windows Server 2012, select the Command Prompt window to bring it in focus. You do not need to open a command prompt with elevated user rights on Server Core installations.
- Change directories to the location of the Windows Server Migration Tools deployment folder.
- Type the following to reverse the registration of Windows Server Migration Tools cmdlets, and then press Enter.
- When SmigDeploy.exe has finished, delete the Windows Server Migration Tools deployment folder and its contents.
Source computers running full and Server Core installation options of Windows Server 2008 R2
To remove Windows Server Migration Tools, you must first reverse the registration of Windows Server Migration Tools cmdlets, and then remove the deployment folder.
To remove Windows Server Migration Tools from Windows Server 2008 R2
- Do one of the following.
- On computers that are running the full installation option of Windows Server 2008 R2, open a Command Prompt window with elevated user rights. To do this, click Start, click All Programs, click Accessories, right-click Command Prompt, and then click Run as administrator.
- On computers that are running the Server Core installation option of Windows Server 2008 R2, select the Command Prompt window to bring it in focus. You do not need to open a command prompt with elevated user rights on Server Core installations.
- Change directories to the location of the Windows Server Migration Tools deployment folder.
- Type the following to reverse the registration of Windows Server Migration Tools cmdlets, and then press Enter.
- When SmigDeploy.exe has finished, delete the Windows Server Migration Tools deployment folder and its contents.
Windows Server 2003 or Windows Server 2008 source computers
To remove Windows Server Migration Tools, you must first reverse the registration of Windows Server Migration Tools cmdlets, and then remove the deployment folder.
To remove Windows Server Migration Tools from Windows Server 2003 or Windows Server 2008
Curio Pro 13 2012 Film
- Do one of the following.
- On computers that are running Windows Server 2003, open a Command Prompt window by clicking Start, clicking Run, typing cmd, and then pressing Enter.
- On computers that are running Windows Server 2008, open a Command Prompt window with elevated user rights. To do this, click Start, click All Programs, click Accessories, right-click Command Prompt, and then click Run as administrator.
- At a command prompt, change directories to the location of the Windows Server Migration Tools deployment folder.
- Type the following to reverse the registration of Windows Server Migration Tools cmdlets, and then press Enter.
- When SmigDeploy.exe has finished, delete the Windows Server Migration Tools deployment folder and its contents.
See Also
Developer: Zengobi
Price: $99 (home); $149 (professional); $69 (K-12/educational)
Requirements: Mac OS X 10.4
Curio Pro 13 2012 Battery
Universal: Yes
Trial: Fully-featured (15 days); 60-day extensions available.
A lot has progressed since ATPM’s review of Curio 2.4. No longerjust a virtual whiteboard or collection bucket for project data, Curiohas matured into a fully-featured project planning suite. Version 4,Zengobi’s recent release, brings even more goodies to the mix forstill better project development.
Felt Needs
Why do you need a project planning application? Most of us haveundertaken projects that go beyond a simple task list, something morethan a simple word processor or even a GTD application could tackle in ahelpful way. When it comes to developing these into well-planned (andtherefore, usually, well-executed) projects, a specialized tool likeCurio can be the very thing you’ll want to pull from your toolbox.
Zengobi likes to encourage creativity—that’s one of the core conceptsbehind Curio—and along those lines they have provided a few profiles of users in differentenvironments: artists and designers, of course, but also a professor, asoftware developer, and an entrepreneur. If you’re wondering how (or if)Curio might be helpful in your workflow, you will find these helpfulstarting points to think about how to use it.
What’s New
I’m not going to re-cover the ground that Matthew did in the first review,instead assuming you’ve read that review. Since version 2.4, however, alot—and I mean really, a lot—has been added to make Curio a much morecomplete package.
Version 3—a full generation behind the current release—introduced theProject Center and Presentation mode. It also improved searching,including use of metadata like tags and timestamps. Integration wasboosted as well, most notably with the addition of iCal and Webarchiving support. Many other features were also brought in; therelease notes for version 3 will walk youthrough these great improvements. Later 3.x updates brought iPhotointegration, a universal binary, and speed/performance increases.
With the recent release of version 4, Zengobi has built in a number ofkey features that enhance existing abilities and add new ones. Majoradditions include mind-mapping, the Shelf, and greater control over theparameters about projects. I’ll elaborate on each of these in a moment.
Other improvements include better formatting styles, tagging, and“adornments” such as flags. Also, further integration and import/exportsupport has been added, along with easier list-management through newkeyboard shortcuts. A number of other features and improvements have beenadded; you can read about them in detail in the version 4 release notes.
The major additions, though are the first three I mentioned above. Tobegin with, mind-mapping expands the abilities of Curio to be a completebrainstorming appliance. For the uninitiated, mind-mapping is adiagram-like rendering of words or ideas, including connections andlinks between them; the concept was formalized by Tony Buzan, who codified some best practices foreffective mind-mapping. Because of its flexible structure and adaptiveapproach to the introduction of new ideas, mind-mapping is preferred bymany for note-taking, early-stage project planning, and generalbrainstorming.
There are several good mind-mapping tools available for Macs, but mostof them are stand-alone operations; Curio’s integration of mind-mappingwithin a larger planning framework, therefore, makes it a more idealsolution for those who wish to include their mind-maps as an ongoingpart of their planning, rather than just a starting point. (To be fair,Curio is not the only project manager that offers this; others, such asConceptDraw also include mind-mappingin their project-planning suites.)
As mind-mapping applications go, Curio’s is good. It’s easy to do arapid-entry style mind-map, so brainstorming can flow without thedistraction of having to right-click on cells or pull down menus tocreate sibling or child cells. Editing your maps once they are done isalso easy—the provided inspector allows you to quickly change the colorof cells and lines, their shapes, and even the fonts and text size.
One key mind-mapping concept appears to be missing, though: you cannotcreate links between sibling cells, nor can you connect one cell withmultiple other cells. Therefore, each idea must remain purelyhierarchical in relation to other represented ideas. In this way, Curiohas only a diagramming interface that is very similar to mind-maps, butnot a true mind-map element.
Shelf
Curio Pro 13 2012 Model
The shelf, another core addition to version 4, offers a real range offunction to Curio. Think of the Shelf as a dynamic Inspector with morecapability than any Inspector you’ve ever seen. In fact, the Inspectoritself lives on the Shelf, but so does a Snippets module (like amulti-page clipboard), a Search module for both searching metadatawithin a Curio project and also applying it, and the Flashlight module,which is an adaptation of Mac OS X 10.4.x’s Spotlight, allowing you tosearch your hard drive for a file you would like to add to a project.These modules are powerful, and deserve some attention to learn themwell. For example, the Snippets module includes a Snippets service,giving you the ability to quickly add any clipping from any applicationto the Snippets, whether Curio is currently running or not.
The final major addition (in my opinion) is the expansion of tools formanaging projects that are underway. Now, tools for better delegation,assigning priority to specific tasks within a project, and indicatingprogress toward completion are all readily at hand. This makes Curio abetter tool for collaborative work and extends its usefulness beyondjust the planning stage more completely.
The other updates and additions are good and useful tools. I wouldencourage you to explore them more through Curio’s Web site, rather thangoing into great detail here.
Using Curio
So, how well does it work? Well, my first impression of Curio was that Iwasn’t sure what I was looking at. Because Curio does so much, it is notlike opening an application with a specific function: when you firstdownload, say, a new word processor, you have some clear preconceptionof what that program is supposed to do, and you contextualize all thebuttons and menus when you first open it. Curio offers a number of verydifferent tools, so even though I was thinking “project planning” when Iopened it up, I felt a little lost at first.
That said, Curio includes a project file of its own, entitled “Welcometo Curio!” This file automatically opens the first time Curio islaunched, and it provides a comprehensive introduction to all that Curiocan do, and is easy to follow along with. The introduction will quicklyhelp you overcome a sense of being lost, just as it did for me. Irecommend reading through this completely before you dig in too deeplywith planning your own projects. [NB: this file is a few years old, anddoesn’t include coverage of new features like the Shelf ormind-mapping.]
Once I began to use Curio to plan, however, I found that its tools aregreat for all stages of project planning. For example, Dossier is awonderful template for outlining the basic motivations of a project:project title, when it was assigned, and by whom are included, as wellas core concepts like overview, background, resources, and deliverables.Having quick access to this list alone is helpful.
Idea spaces are a key concept for Curio—they are where you do much ofyour planning. Whether you plan best with text, graphs, drawings, orpictures, you can create unlimited numbers of idea spaces for yourproject. If you use a tablet such as a Wacom, you may use it on ideaspaces as well, to draw, scribble, or edit—making note-taking inmeetings or planning sessions even easier.
As suggested above, Curio doesn’t assume that all resources for projectswill be created and maintained in Curio—instead, you can add in URLs,documents, images, movies, audio—just about any type of file that mightbe useful. In fact, it is easy to create new documents from Curio withother applications, using the Instant Document feature, which launchesthe specified application and automatically links the created documentto that project.
It’s also nice how well Curio cooperates with other applications forimporting and exporting. You can drag an iCal event to Curio, and itwill be added to the idea space and tracked. Import an outline fromOmniOutliner or another outliner in OPML format, and it will beautomatically added as a list. Paste an e-mail into an idea space easilyfrom Mail. Export project files as a photo album to iPhoto, or uploadthem to .Mac. Curio is not a group project planner, but it is easy tomail the whole project to your team via Mail or other e-mail clients,either in the Curio format (giving them editing options) or as PDF.
Concluding Thoughts
Overall, I am quite satisfied with Curio. I tend to keep a lot ofprojects in process at once, and having one application to be a centralorganizer for them is very useful. I’d like to see some furtherintegrations improvements, like more interactivity with iCal for eventsand tasks. I’d also like to see the mind-map module offer truemind-mapping, and I’d like those maps to be able to be converted tolists or outlines. And I’d like a bit more for working with teams—morecollaboration tools.
There are also some key parts of traditional project management that aremissing. Curio does a good job supporting task lists, but there isnothing built into Curio for contingent tasks, or for understanding therelationships between one task and others. Many project management toolsinclude charting functions for Gantt charts, for example, that will showyou graphically on a time line what tasks must be completed beforeothers can begin. This is a key concept for good resource management,and it is a glaring omission in Curio.
One more caveat as you consider Curio: pay attention to the differencesbetween the Home, Pro, and K12/Education versions. The Home version iscertainly a very good buy, but it lacks a few of the features that I foundso helpful, such as the Dossier and Project sharing via e-mail. Thesefeatures, available only in the other two versions, make the higherprice worth it to me; your needs may vary, of course. The Pro versionalso offers a bit more customization, including a few different “modes”like full-screen and mini mode. The K12 version, while offering all ofthe Pro features, also has some built-in filters for profanity andaccess restrictions, as well as school-appropriate templates and Sleuthsites. All versions fit their intended markets well, but there is enoughvariance that care in choosing is, as always, a good idea.
Other than these few problems, however, I’ve found Curio a capableproject manager. For the money, it’s a great buy; the Home version isnot crippled by any means, and if you qualify for the educationaldiscounts then the price is even better. Professionals will want the Proversion, but even that is reasonably and competitively priced. Those whoneed the missing features I mentioned will want to wait or searchelsewhere; anyone else, however, should find Curio to be moneywell-spent.
Copyright © 2007 Ed Eubanks, Jr. Reviewing inATPM is open to anyone. If you’re interested, write to us [email protected].