Put the VSO Network into Production in Software

Draw QR Code ISO/IEC18004 in Software Put the VSO Network into Production

TIP In the worst-case scenario, you can use NT Backup to back up the file services from your legacy

servers and restore them to your new server, then use Microsoft s Security Migration Editor, which is free with Windows Server 2008, to perform SID regeneration on your files Remember that NT Backup is not available on WS08 and must be downloaded (see 11)

As mentioned earlier, the role of the file server is changing as organizations move toward better and more efficient collaboration tools As such, you might find that it is much more practical for you to create SharePoint sites to host shared documents and other data rather than re-creating a very large number of file shares, as you had in your legacy network If you decide to move to this model, you will not be migrating files from legacy file shares to new file servers, but rather, you will be moving files from legacy file shares to new SharePoint sites that are designed to host more comprehensive collaboration There is still room for the file server, however Users have their own document space on their desktops a document space that needs protection just as much as centralized file shares This document space is stored in the user profile 7 discussed the use of folder redirection, possibly linked to roaming profiles, to provide a more thorough protection policy for end-user data, as well as providing a better strategy for long-term profile management You may, therefore, find that the actual file server migrations you perform are focused more on user and perhaps administrative data than on shared data If this is the case, then focus on the migration of data to Windows SharePoint Services instead of on file servers

excellent idea to use a WSS team site to provide an online users manual to all end users This way, they will know exactly what is going on in their new network In fact, the migrations you perform should be mapped out to the new file services you deploy 8 outlined how your file services should be structured (see Figure 12-10) These are the shared folders you need to focus on Table 12-2 outlines how each type of file service should be migrated

Base article number 829885 at http://supportmicrosoftcom/defaultaspx scid=kb%3b%5bLN% 5d%3b829885 Microsoft also offers a Solution Accelerator for the consolidation of file and print servers Solution Accelerators are a set of documentation and tools to provide simpler operation of complex tasks It can be found at http://gomicrosoftcom/fwlink/ linkid=24719&clcid=0x409 You ll rarely have the occasion to migrate data when it isn t in use, unless you perform the migration during weekends or during times when your servers are shut down Even then, it is difficult to find enough time to perform the migration Most likely, you will be migrating data when users are online and need access to it This is why running source file servers and target systems in parallel is the ideal situation Make sure you communicate your plans to end users to limit the number of Help desk calls the migration may generate If users are left with tasks to perform, then make sure these tasks are clearly outlined and detailed for them in your communications to them The first step in any file server migration is to run reports on your existing file shares, but unless you are running Windows Server 2003 R2 on the source servers, you won t have any

Part VI:

built-in tools to create these reports You ll have to manually check files as you migrate them You can, however, migrate the files and once they are migrated, generate usage reports on the new servers through the File Server Resource Management Reporting feature