Showing posts with label ServerMigrator. Show all posts
Showing posts with label ServerMigrator. Show all posts
Friday, August 3, 2012
Migrate Local Server Accounts to Domain Accounts
ADUM Server Edition, using the ServerMigration App, will convert local server user accounts and local groups to domain accounts and maintain resource security without user impact or downtime..
This process will recreate the source account in the target domain and in any selected OU.
User properties are copied to the converted domain accounts including passwords.
Local groups can be converted into domain local groups then populated with the new migrated domain user accounts.
Once the accounts are created, the source server is reACLed for files, folders and shares using an append process, whereby both the local accounts and domain accounts have the same access to resources. This is done because of the different SIDs between local and domain accounts.
The last step, once satisfied, know as the cleanup process, is to remove the local accounts from the server and the resources.
ADUM also includes third party free tools to automatically repermission SQL databases with the new accounts
Because ADUM Server Edition includes 1 hour of support, once purchased a ManageRED Migration Expert can get the client started with the the process of converting local accounts to domain accounts.
ServerMigrator is the ONLY software to perform this task on the market today.
Learn more about ADUM
Learn more about ServerMigrator
Sunday, April 3, 2011
WADMigrator-ServerMigrator Permission Issues
Windows 7 Operating Systems - Desktop/Laptops:
Issue:
Unable to install the scheduling service client on any Windows 7 workstation within the environment. Console indicates that “the installation path cannot be determined”
Diagnosis:
Remote Registry is set to Manual and is not started
UAC is enabled on the workstations
Resolution:
Set the Remote Registry service to Automatic
Disable UAC on the Windows 7 Desktops/laptops/Tablets/Workstations.
Both Items can be modified via Active Directory Group Policy. The latter policy requires a reboot.
Windows 2008 Server’s
Issue:
Unable to install the scheduling service client on any Windows 2008 Servers within the environment. Console indicates that “the installation path cannot be determined”
Diagnosis:
UAC is not completely disabled. The following registry key has the following value set:
HKLM\Software\Microsoft\Windows\Currentversion\Policies\System\ConsentPromptBehaviorUser. This key has a value set to 1. This is not the default setting.
An explanation of this setting is as follows:
User Account Control: Behavior of the elevation prompt for standard users
The User Account Control: Behavior of the elevation prompt for standard users policy setting controls the behavior of the elevation prompt for standard users.
The options are:
Automatically deny elevation requests. When an operation requires elevation of privilege, a configurable access denied error message is displayed. An enterprise that is running desktops as standard user may choose this setting to reduce help desk calls. *****Has a value of 0 in the registry*****
Prompt for credentials on the secure desktop. (Default) When an operation requires elevation of privilege, the user is prompted on the secure desktop to enter a different user name and password. If the user enters valid credentials, the operation continues with the applicable privilege. *****Has a value of 3 in the registry*****
Prompt for credentials. When an operation requires elevation of privilege, the user is prompted to enter an administrative user name and password. If the user enters valid credentials, the operation continues with the applicable privilege. *****Current Setting****** and has the value of 1
These are the available settings:
0 = Automatically deny elevation requests
1 = Prompt for credentials on the secure desktop
3 (Default) = Prompt for credentials on the secure desktop
Please refer to the following link: http://technet.microsoft.com/en-us/library/dd835564(WS.10).aspx#BKMK_StandardUserPromptBehavior
Resolution:
On all Windows 2008 Servers, the ConsentPromptBehaviorUser key must have a value of 3 (which is the default Windows 2008 setting). A reboot is not necessary for this change to take effect.
The above changes are mandatory and were part of the Checklist provided to the customer as part of the pre-migration checklist.
Special Thanks
A special Thanks goes to Bruno Zaffino from Compucom for his diligence and relentless effort to trouble shoot the challenges faced by the domain migration at the Government of Ontario Migration Project.
Issue:
Unable to install the scheduling service client on any Windows 7 workstation within the environment. Console indicates that “the installation path cannot be determined”
Diagnosis:
Remote Registry is set to Manual and is not started
UAC is enabled on the workstations
Resolution:
Set the Remote Registry service to Automatic
Disable UAC on the Windows 7 Desktops/laptops/Tablets/Workstations.
Both Items can be modified via Active Directory Group Policy. The latter policy requires a reboot.
Windows 2008 Server’s
Issue:
Unable to install the scheduling service client on any Windows 2008 Servers within the environment. Console indicates that “the installation path cannot be determined”
Diagnosis:
UAC is not completely disabled. The following registry key has the following value set:
HKLM\Software\Microsoft\Windows\Currentversion\Policies\System\ConsentPromptBehaviorUser. This key has a value set to 1. This is not the default setting.
An explanation of this setting is as follows:
User Account Control: Behavior of the elevation prompt for standard users
The User Account Control: Behavior of the elevation prompt for standard users policy setting controls the behavior of the elevation prompt for standard users.
The options are:
Automatically deny elevation requests. When an operation requires elevation of privilege, a configurable access denied error message is displayed. An enterprise that is running desktops as standard user may choose this setting to reduce help desk calls. *****Has a value of 0 in the registry*****
Prompt for credentials on the secure desktop. (Default) When an operation requires elevation of privilege, the user is prompted on the secure desktop to enter a different user name and password. If the user enters valid credentials, the operation continues with the applicable privilege. *****Has a value of 3 in the registry*****
Prompt for credentials. When an operation requires elevation of privilege, the user is prompted to enter an administrative user name and password. If the user enters valid credentials, the operation continues with the applicable privilege. *****Current Setting****** and has the value of 1
These are the available settings:
0 = Automatically deny elevation requests
1 = Prompt for credentials on the secure desktop
3 (Default) = Prompt for credentials on the secure desktop
Please refer to the following link: http://technet.microsoft.com/en-us/library/dd835564(WS.10).aspx#BKMK_StandardUserPromptBehavior
Resolution:
On all Windows 2008 Servers, the ConsentPromptBehaviorUser key must have a value of 3 (which is the default Windows 2008 setting). A reboot is not necessary for this change to take effect.
The above changes are mandatory and were part of the Checklist provided to the customer as part of the pre-migration checklist.
Special Thanks
A special Thanks goes to Bruno Zaffino from Compucom for his diligence and relentless effort to trouble shoot the challenges faced by the domain migration at the Government of Ontario Migration Project.
Tuesday, February 15, 2011
New Winzero ScheduleManager
A new version for the Winzero ScheduleManager has been released as an update or as a standalone application.

To download the new ScheduleManager
Navigate to http://www.winzero.ca/downloads/ScheduleManager021611.zip and save it to your computer.
To add the update to any Winzero applicaton including: ServerMigrator, WADMigrator or AccessReporter, unzip the download to drive:\Winzero\ApplicationName\ and allow it to over write any files.
To use ScheduleManager as a standalone application, create a folder and unzip the download into the new folder. Navigate to the folder and double click ScheduleManager to launch.
What's new In ScheduleMnager
- ScheduleManager now supports Windows 2008R2 and Windows 7 64bit
- Import computers from WADMigrator Projects
- Quick deployment Status Reports to reduce overhead
To download the new ScheduleManager
Navigate to http://www.winzero.ca/downloads/ScheduleManager021611.zip and save it to your computer.
To add the update to any Winzero applicaton including: ServerMigrator, WADMigrator or AccessReporter, unzip the download to drive:\Winzero\ApplicationName\ and allow it to over write any files.
To use ScheduleManager as a standalone application, create a folder and unzip the download into the new folder. Navigate to the folder and double click ScheduleManager to launch.
What's new In ScheduleMnager
- ScheduleManager now supports Windows 2008R2 and Windows 7 64bit
- Import computers from WADMigrator Projects
- Quick deployment Status Reports to reduce overhead
Sunday, November 28, 2010
Compare the Top 3 Server Migration Software Solutions
If you are faced with a server migration project, select the best software solution that meets your technical needs and your budget.
We compare the top three (3) server migration software packages on the market today to see how they stack up.

WinzeroTECH ServerMigrator information
ManageRED Resemble information
ScriptLogic SecureCopy information
We compare the top three (3) server migration software packages on the market today to see how they stack up.

WinzeroTECH ServerMigrator information
ManageRED Resemble information
ScriptLogic SecureCopy information
Sunday, July 18, 2010
ServerMigrator v7.0 - Windows 2008 R2
To successfully migrate local account passwords to or from Windows Server 2008R2, after insatalation of ServerMigrator v7.0x, verify the following registry entries for the Lsa key:

Click image to enlarge
The keys must be exactly as illustrated... if you need to make changes the server must be rebooted before the change will take effect.

Click image to enlarge
The keys must be exactly as illustrated... if you need to make changes the server must be rebooted before the change will take effect.
Monday, February 1, 2010
Top Five Server Migration Mistakes.
1. Server Downtime
Server downtime is probably the most-heard concern when performing a migration. This is because most migration processes require the source server be offline, either during the conversion process or during the recovery. However the Winzero solution doesn't require the server to be offline and not accessible to the users.
Winzero's ServerMigrator has addressed this issue through real-time replication that transfers the data to the new platform while the server and application remain online and available to users and then failover with minimal interruption. This process minimizes downtime for business-critical systems for disaster recovery, so why not use it for a server migration?
2. Late Night and Weekends
Get your weekends back. One of the greatest myths about server migrations is that they need to be performed during off-hours when no one is using the servers or server data that is being migrated. This is usually because the server migration can't capture changes to the data after the migration starts.
This isn't the case with asynchronous replication migration products, where data can change on the older server and replicate to the migration target server in real time. With ServerMigrator, real-time replication, migrations can be performed during normal business hours and then failed over to the target server once all the data changes have been captured and transferred to the new system.
3. P2V Conversion Process Failed
We have heard of many people complaining about the pain of the P2V (physical to virtual) process or virtual server migration they are going through, but they can't be bothered to spend a couple hundred dollars for a product that works and can make the nightmare go away.
We can't say we have much sympathy for those who try to perform mission critical functions with free tools that promise the world, but we do respect their tenacity.
4. Compatability Issuses
I hate when that happens.
There is nothing worse than getting within spitting distance of the finish line and breaking your leg. Some of the most common mistake that we have seen occur because of not preparing for the migration by reading the pre-migration checklist prior to starting the migration.
Download the Winzero Premigration Checklist with the migration product before you begin the migration.
A little planning can go along way, but having a tested process that can perform consistently and also minimize downtime will keep you from pulling out your hair.
5. Migration Succeeded but Users are Locked Out.
So, the migration's been completed, only none of the users can logon, and there begins a whole new nightmare.
There are many reasons why this happens, and it could be any combination of the factors mentioned above. Is it the free tool that was downloaded to perform the migration, the hardware being migrated, or the virtual platform? Who knows, but ServerMigrator allows you to "set and forget" and avoid this monster of user account and password conflict issues.
In summary, perform your server migration and ask what works best and what to avoid. Learn more about server provisioning or performing successful server migrations with Winzero serverMigrator or Winzero ServerMigrator Lite.
Server downtime is probably the most-heard concern when performing a migration. This is because most migration processes require the source server be offline, either during the conversion process or during the recovery. However the Winzero solution doesn't require the server to be offline and not accessible to the users.
Winzero's ServerMigrator has addressed this issue through real-time replication that transfers the data to the new platform while the server and application remain online and available to users and then failover with minimal interruption. This process minimizes downtime for business-critical systems for disaster recovery, so why not use it for a server migration?
2. Late Night and Weekends
Get your weekends back. One of the greatest myths about server migrations is that they need to be performed during off-hours when no one is using the servers or server data that is being migrated. This is usually because the server migration can't capture changes to the data after the migration starts.
This isn't the case with asynchronous replication migration products, where data can change on the older server and replicate to the migration target server in real time. With ServerMigrator, real-time replication, migrations can be performed during normal business hours and then failed over to the target server once all the data changes have been captured and transferred to the new system.
3. P2V Conversion Process Failed
We have heard of many people complaining about the pain of the P2V (physical to virtual) process or virtual server migration they are going through, but they can't be bothered to spend a couple hundred dollars for a product that works and can make the nightmare go away.
We can't say we have much sympathy for those who try to perform mission critical functions with free tools that promise the world, but we do respect their tenacity.
4. Compatability Issuses
I hate when that happens.
There is nothing worse than getting within spitting distance of the finish line and breaking your leg. Some of the most common mistake that we have seen occur because of not preparing for the migration by reading the pre-migration checklist prior to starting the migration.
Download the Winzero Premigration Checklist with the migration product before you begin the migration.
A little planning can go along way, but having a tested process that can perform consistently and also minimize downtime will keep you from pulling out your hair.
5. Migration Succeeded but Users are Locked Out.
So, the migration's been completed, only none of the users can logon, and there begins a whole new nightmare.
There are many reasons why this happens, and it could be any combination of the factors mentioned above. Is it the free tool that was downloaded to perform the migration, the hardware being migrated, or the virtual platform? Who knows, but ServerMigrator allows you to "set and forget" and avoid this monster of user account and password conflict issues.
In summary, perform your server migration and ask what works best and what to avoid. Learn more about server provisioning or performing successful server migrations with Winzero serverMigrator or Winzero ServerMigrator Lite.
Thursday, September 24, 2009
How to Uninstall Software With Winzero Schedule Service
To uninstall any Winzero software application that distributes the Winzero Schedule Service, requires a three step process
1) Remove folders and files from the remote computers.
2) Remove the Scheduling Service from the remote computers
3) Uninstall the software.
Remove any Remote Files
Select the computers to remove the Winzero remote files
From the Menu select Configuration
Select Remove Remote Files...
Repeat until all remote files have been removed from all computers
Uninstall the Winzero Scheduling Service
From the Menu Configuration
Select Manage Computer Schedule Service......
From the Popup Window Select one or more computers
From the Menu Select ACTION
Select Remove Scheduling Service
Once the service removal is complete double-Click the computer name to verify the service is not installed.
Close the ScheduleManager Window
Uninstall the Winzero Application
Exit the Winzero Application
From the Start Button Select Winzero
From the flyout select Uninstall
Select one or more Winzero Applications, from the list of Winzero Applications
Click Uninstall.
1) Remove folders and files from the remote computers.
2) Remove the Scheduling Service from the remote computers
3) Uninstall the software.
Remove any Remote Files
Select the computers to remove the Winzero remote files
From the Menu select Configuration
Select Remove Remote Files...
Repeat until all remote files have been removed from all computers
Uninstall the Winzero Scheduling Service
From the Menu Configuration
Select Manage Computer Schedule Service......
From the Popup Window Select one or more computers
From the Menu Select ACTION
Select Remove Scheduling Service
Once the service removal is complete double-Click the computer name to verify the service is not installed.
Close the ScheduleManager Window
Uninstall the Winzero Application
Exit the Winzero Application
From the Start Button Select Winzero
From the flyout select Uninstall
Select one or more Winzero Applications, from the list of Winzero Applications
Click Uninstall.
Monday, August 24, 2009
Windows Server Migration Checklist - ServerMigrator

Before beginning a server migration project, a number of mandatory prerequisites are needed to be met in order to complete a server migration successfully. These requirements are standards to meet both the requirements for Microsoft Windows server security and the Winzero ServerMigrator software.
Download the Server Migration Checklist
Wednesday, March 25, 2009
IMPORTANT Update Available
Bulletin: 032509
Software Effected:
ServerMigrator and AcessReporter
Issue:
An important issue has come to our attention for ServerMigrator v6.00 Build 031709 and AccessReporter V3.05 Build 032309. The new Add/Remove Domains or workgroups feature was unable to verify or add domains. This has been fixed and the update fix has been added to the updater. Both ServerMigrator and AccessReporter build after the fix is 032509 or newer.
Winzero would like to thank Michael Heredia from the University of North Texas for bringing this issue to light.
Solution
To update to the latest fixed build of ServerMigrator or AccessReporter, a new Check for Updates has been added to each product. Select check for updates from the Menu bar > Help > Check for Updates.
Caution: Once the CheckforUpdates starts, be sure that ServerMigrator or AccessReporter is completely closed. With most updates, the executable and the Main GUI are replaced. If the application is not completely closed the updater will not be able to replace these files with the new updates
Software Effected:
ServerMigrator and AcessReporter
Issue:
An important issue has come to our attention for ServerMigrator v6.00 Build 031709 and AccessReporter V3.05 Build 032309. The new Add/Remove Domains or workgroups feature was unable to verify or add domains. This has been fixed and the update fix has been added to the updater. Both ServerMigrator and AccessReporter build after the fix is 032509 or newer.
Winzero would like to thank Michael Heredia from the University of North Texas for bringing this issue to light.
Solution
To update to the latest fixed build of ServerMigrator or AccessReporter, a new Check for Updates has been added to each product. Select check for updates from the Menu bar > Help > Check for Updates.
Caution: Once the CheckforUpdates starts, be sure that ServerMigrator or AccessReporter is completely closed. With most updates, the executable and the Main GUI are replaced. If the application is not completely closed the updater will not be able to replace these files with the new updates
Thursday, March 12, 2009
New Check for Updates Feature
Bulletin: 031209
Software Effected:
ServerMigrator and Winzero Active Directory Migrator
New Feature:
To keep current with the latest build of ServerMigrator or WADMigrator, a new Check for Updates has been added to each product. Before begining a new project, check for updates from the Menu bar > Help > Check for Updates.
Caution: Once the CheckforUpdates starts, be sure that ServerMigrator or WADMigrator is completely closed. With most updates, the executable and the Main GUI are replaced. If the application is not completely closed the updater will not be able to replace these files with the new updates
Software Effected:
ServerMigrator and Winzero Active Directory Migrator
New Feature:
To keep current with the latest build of ServerMigrator or WADMigrator, a new Check for Updates has been added to each product. Before begining a new project, check for updates from the Menu bar > Help > Check for Updates.
Caution: Once the CheckforUpdates starts, be sure that ServerMigrator or WADMigrator is completely closed. With most updates, the executable and the Main GUI are replaced. If the application is not completely closed the updater will not be able to replace these files with the new updates
Sunday, February 22, 2009
Access Denied Using Multiple Server Names (OptionalNames)
Bulletin: 022109
Software Effected:
ServerMigrator - multiple server name feature
Issue:
Using the multiple name feature (OptionalNames) in ServerMigrator to assign both the old and new server name to the target server, the new server name and the old server name are both reachable by ping, DNS is working correctly and the old server has been shut down however access is denied.
When clients try to connect to a share using the old server name. Access is denied. Logon Failure: target account name is incorrect.
The following error appears in the event viewer when accessing the old server UNC name:
The kerberos client received a KRB_AP_ERR_MODIFIED error from the server host/OldServerName/domainName. This indicates that the password used to encrypt the Kerberos service ticket is different than that on the target server. Commonly, this is due to identically named machine accounts in the target realm and the client realm. Please contact your system administrator.
Solution:
For Windows 2003 or newer servers, for the OptionalNames value to work correctly edit or add the following Registry entry.
HKLM\System\CurrenControlSet\Services\LanmanServer\Parameters
DisableStrictNameChecking
REG_DWORD=1
for DNS aliasing to work.
The final solution to this issue was finally resolved thanks to our client, Ken Jackson at Malco Products Inc., (www.malcopro.com) in Barberton, Ohio.
After using ServerMigrator to add additional names to a server, change the DNS setting of the old server to point to the new server IP address and verify that the registry settings are correct, Manually remove the old server name from the domain using the Active Directory User and Computers MMC. Once deleted, add the old server name to Active Directory again and reboot the server with the two names.
Once again our thanks go to Ken Jackson for his efforts in resolving this issue.
Software Effected:
ServerMigrator - multiple server name feature
Issue:
Using the multiple name feature (OptionalNames) in ServerMigrator to assign both the old and new server name to the target server, the new server name and the old server name are both reachable by ping, DNS is working correctly and the old server has been shut down however access is denied.
When clients try to connect to a share using the old server name. Access is denied. Logon Failure: target account name is incorrect.
The following error appears in the event viewer when accessing the old server UNC name:
The kerberos client received a KRB_AP_ERR_MODIFIED error from the server host/OldServerName/domainName. This indicates that the password used to encrypt the Kerberos service ticket is different than that on the target server. Commonly, this is due to identically named machine accounts in the target realm and the client realm. Please contact your system administrator.
Solution:
For Windows 2003 or newer servers, for the OptionalNames value to work correctly edit or add the following Registry entry.
HKLM\System\CurrenControlSet\Services\LanmanServer\Parameters
DisableStrictNameChecking
REG_DWORD=1
for DNS aliasing to work.
The final solution to this issue was finally resolved thanks to our client, Ken Jackson at Malco Products Inc., (www.malcopro.com) in Barberton, Ohio.
After using ServerMigrator to add additional names to a server, change the DNS setting of the old server to point to the new server IP address and verify that the registry settings are correct, Manually remove the old server name from the domain using the Active Directory User and Computers MMC. Once deleted, add the old server name to Active Directory again and reboot the server with the two names.
Once again our thanks go to Ken Jackson for his efforts in resolving this issue.
Saturday, November 22, 2008
NTFS Displays SIDs Only After Migration
Bulletin: 112208
Software Effected:
ServerMigrator
Issue:
A new bug has Just recently come to our attention. When migrating from a member server to a member server NTFS security on the target server is not translated to the New SIDs of the target server. To date only three clients have experienced this issue.
Solution:
We and Sylvain Martel of CSPQ (give credit where credit is due) have identified this issue and Winzero has resolved it with ServerMigrator v5.11 and up.
When migrating member servers with server names that end with a number the Windows API adds a (o) zero to the end of the target server name and ServerMigrator cannot resolve the SID of the target server.
Starting November 23th with ServerMigrator version 5.11 the target server name issue has been resolved.
New Update Releases:
ServerMigrator2007 version 5.11
Software Effected:
ServerMigrator
Issue:
A new bug has Just recently come to our attention. When migrating from a member server to a member server NTFS security on the target server is not translated to the New SIDs of the target server. To date only three clients have experienced this issue.
Solution:
We and Sylvain Martel of CSPQ (give credit where credit is due) have identified this issue and Winzero has resolved it with ServerMigrator v5.11 and up.
When migrating member servers with server names that end with a number the Windows API adds a (o) zero to the end of the target server name and ServerMigrator cannot resolve the SID of the target server.
Starting November 23th with ServerMigrator version 5.11 the target server name issue has been resolved.
New Update Releases:
ServerMigrator2007 version 5.11
Tuesday, November 11, 2008
Password Copy Issue
Bulletin: 111108
Software Effected:
ServerMigrator, PasswordCopy and WADMigrator
Issue:
Just recently Microsoft has released an update that is preventing passwordcopy from accessing the system32 directory that a number of our clients started experiencing in the last week.
Solution:
We have identified this issue and have resolved it. There will be a new ServerMigrator and PasswordCopy available starting November 12th that over rides the password copy problem some of our clients were experiencing.
New Update Releases:
ServerMigrator2007 version 5.10
PasswordCopy32 version 3.00
WADMigrator version 5.00
* PasswordCopy Server Edition and Domain Edition will be repalced with PasswordCopy32 followed by PasswordCopy64.
Software Effected:
ServerMigrator, PasswordCopy and WADMigrator
Issue:
Just recently Microsoft has released an update that is preventing passwordcopy from accessing the system32 directory that a number of our clients started experiencing in the last week.
Solution:
We have identified this issue and have resolved it. There will be a new ServerMigrator and PasswordCopy available starting November 12th that over rides the password copy problem some of our clients were experiencing.
New Update Releases:
ServerMigrator2007 version 5.10
PasswordCopy32 version 3.00
WADMigrator version 5.00
* PasswordCopy Server Edition and Domain Edition will be repalced with PasswordCopy32 followed by PasswordCopy64.
Friday, August 1, 2008
ServerMigrator Domain Name Resolution
Bulletin: 010808
Software Effected:
ServerMigrator version 5.09 and earlier
Issue:
I am evaluating ServerMigrator to migrate file and rights from an existing 2000 server to 2008. The destination server is a DC as is the source server. When I try to add a domain in ServerMigrator, I get a message "No Domains Found.! Check Network Firewalls, Router netBios Broadcasts, DNS or Wins"
Solution:
We have seen this issue starting to appear recently at the server level. It has to do with Netbios name resolution of the domain name and has been added in a recent Microsoft Update
We have two ways around this until a fix is added to ServerMigrator v5.10 it has been add to our other tools when Vista came out that involved workstations.
In the working directory of ServerMigrator drive:\Winzero\ServerMigrator there is a file called Domains.Add
With NotePad enter the Netbios domain or domain names in capital letters, one entry per line and save the file.
At this point Select Configuration from the menu and Select Add/Remove Servers from the popup window select the domain from the drop down box and you should get a list of servers to add.
If the Available Servers window is empty then you will need to add a lmhost file for name resolution.
Software Effected:
ServerMigrator version 5.09 and earlier
Issue:
I am evaluating ServerMigrator to migrate file and rights from an existing 2000 server to 2008. The destination server is a DC as is the source server. When I try to add a domain in ServerMigrator, I get a message "No Domains Found.! Check Network Firewalls, Router netBios Broadcasts, DNS or Wins"
Solution:
We have seen this issue starting to appear recently at the server level. It has to do with Netbios name resolution of the domain name and has been added in a recent Microsoft Update
We have two ways around this until a fix is added to ServerMigrator v5.10 it has been add to our other tools when Vista came out that involved workstations.
In the working directory of ServerMigrator drive:\Winzero\ServerMigrator there is a file called Domains.Add
With NotePad enter the Netbios domain or domain names in capital letters, one entry per line and save the file.
At this point Select Configuration from the menu and Select Add/Remove Servers from the popup window select the domain from the drop down box and you should get a list of servers to add.
If the Available Servers window is empty then you will need to add a lmhost file for name resolution.
Sunday, February 24, 2008
Windows Server 2008, Upgrade or Migrate?
Bulletin: 022408
Software Effected:
ServerMigrator, RemoveUnknown, Accessreporter, RenameITSE
Issue:
We are planning on deploying Windows Server 2008 shortly, would you recommend upgrading existing servers to Server 2008 or migrating clean to Server 2008?
Are there any steps we should take before rolling out Windows Server 2008?
Solution:
Before you begin, verify hardware and software compatibility before deciding which path to follow.
Regardless of which path you select for deploying Windows Server 2008, we strongly recommend analyzing and cleaning up the old server before moving foward. In either case, "garbage in, garbage out", your end result will only be as sucessful as what you bring into server 2008.
Windows Server 2008 in place upgrade
Winzero recommends the following steps above and beyond the Microsoft upgrade path.
Report and cleanup obsolete users and local groups. Remove disabled accounts and accounts that do not or have not accessed the server for a period of time. Remove local groups with out members or local groups that do not have access to folders or shares.
Report, verify and cleanup File, folder and Share ACLs. Tighten security by removing the everyone group in ACLs.
Report and remove unknown accounts and SIDs in localgroups and files, folders and share ACLs.
Windows Server 2008 Migration
Winzero recommends the following steps above and beyond the Microsoft migration path.
Report and cleanup obsolete users and local groups. Remove disabled accounts and accounts that do not or have not accessed the server for a period of time. Remove local groups with out members or local groups that do not have access to folders or shares.
Report, verify and cleanup File, folder and Share ACLs. Tighten security by removing the everyone group in ACLs.
Report and remove unknown accounts and SIDs in localgroups and files, folders and share ACLs.
if your migration involves server consolidations, report duplicate user names and duplicate localgroups names from the servers that will be combined. Verify if accounts and groups are to be merged or renamed before migrating.
Taking these additional steps before upgrading or migrating to Windows Server 2008 will improve security and provide the fastest time-to-benefit.
Software Effected:
ServerMigrator, RemoveUnknown, Accessreporter, RenameITSE
Issue:
We are planning on deploying Windows Server 2008 shortly, would you recommend upgrading existing servers to Server 2008 or migrating clean to Server 2008?
Are there any steps we should take before rolling out Windows Server 2008?
Solution:
Before you begin, verify hardware and software compatibility before deciding which path to follow.
Regardless of which path you select for deploying Windows Server 2008, we strongly recommend analyzing and cleaning up the old server before moving foward. In either case, "garbage in, garbage out", your end result will only be as sucessful as what you bring into server 2008.
Windows Server 2008 in place upgrade
Winzero recommends the following steps above and beyond the Microsoft upgrade path.
Report and cleanup obsolete users and local groups. Remove disabled accounts and accounts that do not or have not accessed the server for a period of time. Remove local groups with out members or local groups that do not have access to folders or shares.
Report, verify and cleanup File, folder and Share ACLs. Tighten security by removing the everyone group in ACLs.
Report and remove unknown accounts and SIDs in localgroups and files, folders and share ACLs.
Windows Server 2008 Migration
Winzero recommends the following steps above and beyond the Microsoft migration path.
Report and cleanup obsolete users and local groups. Remove disabled accounts and accounts that do not or have not accessed the server for a period of time. Remove local groups with out members or local groups that do not have access to folders or shares.
Report, verify and cleanup File, folder and Share ACLs. Tighten security by removing the everyone group in ACLs.
Report and remove unknown accounts and SIDs in localgroups and files, folders and share ACLs.
if your migration involves server consolidations, report duplicate user names and duplicate localgroups names from the servers that will be combined. Verify if accounts and groups are to be merged or renamed before migrating.
Taking these additional steps before upgrading or migrating to Windows Server 2008 will improve security and provide the fastest time-to-benefit.
Wednesday, December 5, 2007
CreateRemoteThread Failed: 8
Bulletin: 120507
Software Effected:
ServerMigrator, Resemble, PasswordCopy
Issue:
When running the “Convert Local Users and Groups to Domain Accounts” function, I always receive the following errors:
Password Process -- No Password Information to Process
It also displays a command prompt with an error message relating to copypassword, stating “CreateRemoteThread failed: 8”
The outcome is that all the local users are created on the domain as domain accounts, however none of the passwords are copied.
Solution:
CreateRemoteThread failed: 8 is a permissions issue. Any Winzero software that utilizes the passwordcopy function will fail if the software is installed through a MS Terminal Server Client.
You can not install ServerMigrator 2007, PasswordCopy or any Resemble product using a MS Terminal Server session. Once you install the software directly on the computer you can use MS Terminal Server Client or Remote Desktop to remotely run the application.
Software Effected:
ServerMigrator, Resemble, PasswordCopy
Issue:
When running the “Convert Local Users and Groups to Domain Accounts” function, I always receive the following errors:
Password Process -- No Password Information to Process
It also displays a command prompt with an error message relating to copypassword, stating “CreateRemoteThread failed: 8”
The outcome is that all the local users are created on the domain as domain accounts, however none of the passwords are copied.
Solution:
CreateRemoteThread failed: 8 is a permissions issue. Any Winzero software that utilizes the passwordcopy function will fail if the software is installed through a MS Terminal Server Client.
You can not install ServerMigrator 2007, PasswordCopy or any Resemble product using a MS Terminal Server session. Once you install the software directly on the computer you can use MS Terminal Server Client or Remote Desktop to remotely run the application.
Wednesday, November 14, 2007
Migrate Accounts from Workgroup to Domain Server
Bulletin: 111407
Software Effected:
ServerMigrator 2007
Issue:
I am looking for a product that is able to copy local user accounts and passwords from one Windows 2003 server to another Windows 2003 server, one server is in a workgroup, and the other is joined to a domain. Can this be done with any of your products?
Solution:
When Migrating from a member server in a Workgroup (DMZ, Workgroups, Offsite) to a member server that is a member of a domain or a different workgroup the main challenge is connectivity and Administrative rights. Normally to perfom member server to member server migration, one account is required that has rights on both the source server and the target server.
In the case of workgroups the "ADMINISTRATOR" account must be used, the passwords of each account must be the same and there must be connectivity betwen the two server.
Winzero has created another scenario to this situation where one of three requirements can not be met.
NCS Migration (Non Connected Servers).
By installing ServerMigrator on both the source and target servers, the user accounts, passwords, user properties, local groups, local group members, NTFS Folder permissions and share permissions are collect on the source server, translated and then recreated on the target server in two steps.
For detailed information go to ServerMigrator and follow the NCS Migration link
Software Effected:
ServerMigrator 2007
Issue:
I am looking for a product that is able to copy local user accounts and passwords from one Windows 2003 server to another Windows 2003 server, one server is in a workgroup, and the other is joined to a domain. Can this be done with any of your products?
Solution:
When Migrating from a member server in a Workgroup (DMZ, Workgroups, Offsite) to a member server that is a member of a domain or a different workgroup the main challenge is connectivity and Administrative rights. Normally to perfom member server to member server migration, one account is required that has rights on both the source server and the target server.
In the case of workgroups the "ADMINISTRATOR" account must be used, the passwords of each account must be the same and there must be connectivity betwen the two server.
Winzero has created another scenario to this situation where one of three requirements can not be met.
NCS Migration (Non Connected Servers).
By installing ServerMigrator on both the source and target servers, the user accounts, passwords, user properties, local groups, local group members, NTFS Folder permissions and share permissions are collect on the source server, translated and then recreated on the target server in two steps.
For detailed information go to ServerMigrator and follow the NCS Migration link
Tuesday, November 13, 2007
Server Migration From Subfolders
Bulletin: 111307
Software Effected:
ServerMigrator Resemble
Issue:
I want to migrate d:\apps\eng The problem is that in the "Select Source folders tree to migrate" Window, I am unable to select the d:\apps\eng folder for the migration. I can oly select d:\apps. Is it possible to select only the eng folder?. The problem is that I have a lot of folders in d:\apps that I don´t want to migrate.
Solution:
Not being able to migrate from subfolder trees during a server migration is by design. Because Microsoft intoduced parent inheritance in Windows Servers 2000 and up, our clients were getting unwanted folder ACLs based on the target folders rather then the original ACLs. When ServerMigrator or Resemble migrate folders the root folder ACLs are set explicitly without inheritance from the parent and all subfolders follow the inheritance pattern of the source to reflect the original permissions.
To migrate from a subfolder without migrating all sub folders, create a new root folder with permissions that match the original root folder on the source server and temporarily move the desired subfolders to the newly created folder.
Migrate the new Root folder to the destination server. Using this method all folder and subfolder permissions will be correct and all shares will be recreated.
Software Effected:
ServerMigrator Resemble
Issue:
I want to migrate d:\apps\eng The problem is that in the "Select Source folders tree to migrate" Window, I am unable to select the d:\apps\eng folder for the migration. I can oly select d:\apps. Is it possible to select only the eng folder?. The problem is that I have a lot of folders in d:\apps that I don´t want to migrate.
Solution:
Not being able to migrate from subfolder trees during a server migration is by design. Because Microsoft intoduced parent inheritance in Windows Servers 2000 and up, our clients were getting unwanted folder ACLs based on the target folders rather then the original ACLs. When ServerMigrator or Resemble migrate folders the root folder ACLs are set explicitly without inheritance from the parent and all subfolders follow the inheritance pattern of the source to reflect the original permissions.
To migrate from a subfolder without migrating all sub folders, create a new root folder with permissions that match the original root folder on the source server and temporarily move the desired subfolders to the newly created folder.
Migrate the new Root folder to the destination server. Using this method all folder and subfolder permissions will be correct and all shares will be recreated.
Saturday, November 10, 2007
Preserving Old UNC Share Names
Bulletin: 111007
Software Effected:
ServerMigrator Resemble Server Edition
Issue:
I would like to know how I can maintain the same UNC share names to the new server after a server migration.
Solution:
Perserving old server UNC Share paths after a server migration.
Once you have completed your server migration. You must turn the old server off or disconnect it from the network.
On your DNS and WINS Server add or modify the entry for the old server name using the new server IP address
Using ServerMigrator Multi Name feature add the old server name to the new server
Select the new server in the list then from:
Menu > Server Tools > Add Multiple Netbios Names to this Server
Enter the old server name without the \\
Click OK
You may have to reboot the server for the name to take affect.
Also see http://servermigrator.blogspot.com if you are having issues with the server name showing up as a duplicate there is a registry fix
Software Effected:
ServerMigrator Resemble Server Edition
Issue:
I would like to know how I can maintain the same UNC share names to the new server after a server migration.
Solution:
Perserving old server UNC Share paths after a server migration.
Once you have completed your server migration. You must turn the old server off or disconnect it from the network.
On your DNS and WINS Server add or modify the entry for the old server name using the new server IP address
Using ServerMigrator Multi Name feature add the old server name to the new server
Select the new server in the list then from:
Menu > Server Tools > Add Multiple Netbios Names to this Server
Enter the old server name without the \\
Click OK
You may have to reboot the server for the name to take affect.
Also see http://servermigrator.blogspot.com if you are having issues with the server name showing up as a duplicate there is a registry fix
Friday, November 9, 2007
User Must Change Password at Next Logon
Bulletin: 110907-2
Software Effected:
ServerMigrator, Resemble, PasswordCopy, Domainreconfigure
Issue:
After performing a member server migration, the passwords were copied sucessfully but it appears that the accounts are being prompted to change the password at next logon. Is there a setting we can change so users are not prompted to change their passwords?
Solution:
In Windows Server 2000 and 2003, if password is set using the Winzero paswordCopy method, the "user must change password at next logon" attribute is set automatically by the system so users are forced to change the password at next logon.
Winzero password Copy functionality has an extended process to unselect the "User must Change password at next logon" feature. However, server policies or domain policies may over ride this process.
We have included a utility in ServerMigrator to report and manage pasword properties to unselect one or more accounts "user must change password at next logon" property.
A second method, the preferred solution is to use a registry key to control this.
Key: HKEY_LOCAL_MACHINE
Path:\System\CurrentControlSet\Control\Lsa
Value name: SamRestrictOwfPasswordChange
Data type: REG_DWORD
value: 0
If this key does not appear then create it with the value of 0 (zero) if the key does exist then change the value.
Software Effected:
ServerMigrator, Resemble, PasswordCopy, Domainreconfigure
Issue:
After performing a member server migration, the passwords were copied sucessfully but it appears that the accounts are being prompted to change the password at next logon. Is there a setting we can change so users are not prompted to change their passwords?
Solution:
In Windows Server 2000 and 2003, if password is set using the Winzero paswordCopy method, the "user must change password at next logon" attribute is set automatically by the system so users are forced to change the password at next logon.
Winzero password Copy functionality has an extended process to unselect the "User must Change password at next logon" feature. However, server policies or domain policies may over ride this process.
We have included a utility in ServerMigrator to report and manage pasword properties to unselect one or more accounts "user must change password at next logon" property.
A second method, the preferred solution is to use a registry key to control this.
Key: HKEY_LOCAL_MACHINE
Path:\System\CurrentControlSet\Control\Lsa
Value name: SamRestrictOwfPasswordChange
Data type: REG_DWORD
value: 0
If this key does not appear then create it with the value of 0 (zero) if the key does exist then change the value.
Subscribe to:
Posts (Atom)