Winzero Releases the next solution in Active Directory Migration Challenges - Winzero Active Directory Migrator ensuring coexistence between migrated and un-migrated users, simplifing the migration processes with automated resource updating and continued support during and after the migration process.
Whether migrating to meet specific economic challenges or undergoing acquisition, mergers or divestitures, Winzero Active Directory Migrator provides the features necessary to meet your evolving needs and budget.
Friday, February 06, 2009
Winzero Releases WADMigrator
Posted by
AMS
at
9:49 AM
0
comments
Labels: Active Director Migration, Virtual Domain Migration, WADMigrator, Winzero Active directory Migrator
Tuesday, November 11, 2008
PasswordCopy 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.
Posted by
AMS
at
10:00 AM
0
comments
Labels: Password Copy Issue, PasswordCopy
Sunday, October 26, 2008
Virtual Migration Part 6 Custom Remaping
Once the common update process of associating source and target accounts for servers and workstations are complete, the Virtual Consultant will use Winzero addons and scripts to associate source and target SIDs for additional resource that are not part of a standard migration.
The Virtual Consultant will follow a set of guidelines to verify that all unique directories and applications that rely on Netbios Name or SID access are updated.
Using Winzero Update Process Addons
The virtual consultant will verify and update resources as needed using the Winzero Migration Addon Tools for the following resources to maintain coexistance during the migration process.
Roaming or mandatory profiles
Exchange 5.5 account associations
Exchange 200x account associations
SQL Server upto version 7
SQL Server 2000/2005
NAS and SAN Server permissions
Using Winzero Custom Scripting
Using the Winzero scripting utility, the Virtual Consultant will identify any unique applications that require updating and automate the update process for:
Any inhouse applications
Once the update process is complete, the Virtual Consultant will conduct a controlled migration of a typical user to verify that all access to resources has been maintained.
Posted by
AMS
at
10:07 AM
0
comments
Labels: Custom Scripting, Recource Update, Step 6 Virtual Migration, Winzero Addons
Saturday, August 02, 2008
Virtual Migration Part 5 - Resource Remapping
The most crucial aspect of the migration is the Update process. This is how the new target SIDS are associated with the Source SIDS. This processes runs locally on each computer and may take any where from 2 minutes to 5 minutes for workstations and 4 minutes to 6 hours on servers. Because this process is multitasked the total time required is the time required to update the largest server and to locate all workstations. In order for the updater to successfully execute on the remote machine the computer must be online, reachable through DNS or WINS and the account used for the update must have administrative rights locally on the remote computer.
The Virtual Consultant will begin the update process and continue to update all workstations and servers until all computers have been updated using the report information gathered from the Directory Object Extractor Reports.
The Update process runs on the remote computer in the background without disruption to the logged on user. The process appends the target SID of the migrated object every where the source SID has rights or permissions. The Update process appends Local group membership, Share, Folder and File permissions, local profiles, mapped drives, connected printers and user rights.
Using the update method, two essential migration requirements are met. One the virtual consultant running the migration project knows exactly which user and computers are ready to be cut over to the target domain and most importantly the end user now has the exact same rights and permissions in the target domain as they had in the source domain including the same desktop and profile settings.
Posted by
AMS
at
4:24 PM
0
comments
Labels: Profile update, SID remap, Step 5 Virtual Migration, Update process
Tuesday, July 08, 2008
Virtual Migration Part 4 - SIDHistory
Once the mapping files are created and saved, the virtual consultant will perform the SIDHistory portion of the domain migration.
The SID History task allows the source SID of security identified users and groups to be appended to each accounts sIDHistory attribute in Active Directory. The SIDHistory attribute adds an extra token to the accounts security access to resources.
All Winzero domain migrations always utilizes both SIDHistory and the REACL process to maximize endusers access to their resources.
Before begining the sIDHistory migration, the following additional dependencies are required.
Success and failure auditing of account management for both source and target domains.
Windows NT and 200x source domains call this user and group management auditing.
An empty local group in the source domain that is named {SourceNetBIOSDom}$$$.
Check the registry so that:
HKEY_LOCAL_MACHINE
System\CurrentControlSet\Control\LSA\TcpipClientSupport
key is set to 1 on the source domain primary domain controller or PDC Emulator.
You must restart the source domain primary domain controller or PDC emulator after the registry configuration.
If the target domain is a Windows 200x domain, Windows security requires user credentials with administrator rights in the target domain.
Posted by
AMS
at
10:38 AM
0
comments
Labels: SIDHistory, Step 4 Virtual Migration, Virtual Domain Migration