This is not as easy as you think. The path to some of the objects is written into the F00165. So, you might move all of the files and they just might not work anymore… Arrgghhh – what are you going to do…
You put your thinking cap on, and decide that you could rename the new location (via cname) the same as the old location. ie.
and you want to whack them on a new server, say \\newserver
and you still want to reference your chares with \\oldMediaObjLocation
So, you’re smart – you use a cname or an alias which basically (via DNS) points oldMediaObjLocation to newserver – but it does not work.
I get prompted for a username and password or something about the server already exists, which it does not.
So, now you need to do this for 2003:
1. Create the CNAME record for the file server on the appropriate DNS server, if the CNAME record is not already present.
2. Apply the following registry change to the file server. To do so, follow these steps:
1. Start Registry Editor (Regedt32.exe).
2. Locate and click the following key in the registry:
HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\LanmanServer\Parameters
3. On the Edit menu, click Add Value, and then add the following registry value:
Value name: DisableStrictNameChecking
Data type: REG_DWORD
Radix: Decimal
Value: 1
4. Quit Registry Editor.
3. Restart your computer.
Then you’ll be able to reference unc shares that are named via a cname.
So, oyu can move your media objects and they will all still work! Woo hoo!
No comments:
Post a Comment