you can also consider using DFS consolidation roots for an
interims time during the file-migration (see Q829885 - Distributed File System
update to support consolidation roots in Windows: http://support.microsoft.com/?id=829885).
This will leverage the OptionalNames regkey (a little more restrictive than
DisableStrictNameChecking).
btw, the DFS consolidation roots will soon be supported by
the Quest server-consolidation tools (and not only by Microsoft's FSMT... -
which sad, but true, doesn't support migration of local groups and thus cause
issues consolidating data ACL'd with local groups).
/Guido From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Dean Wells Sent: Friday, November 19, 2004 6:39 PM To: Send - AD mailing list Subject: RE: [ActiveDir] OT: Linked files. Note
that if you do decide to use CNAMEs to redirect CIFS/SMB queries to servers
using a.n.other name, you must configure DisableStrictNameChecking in each of
the server's registries.
HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\LanmanServer\Parameters
On the Edit menu, click Add Value, and then add the following registry value: Value name: DisableStrictNameChecking Data type: REG_DWORD Radix/Base: Decimal Value: 1 -- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Jacqui Hurst Sent: Friday, November 19, 2004 11:56 AM To: [EMAIL PROTECTED] Subject: RE: [ActiveDir] OT: Linked files. If you are keeping the same file structures
and just changing the server names can you not setup cnames in DNS to point to
the new servers? Not tried it myself but thought it might be
worth a suggestion. Jacqui From:
[EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]
On Behalf Of Paul van
Geldrop Hi all, A bit offtopic, I realise, but hopefully somebody will
be able to provide an answer. The problem: We're on the verge of consolidating a
rather big load of user files to a new environment. However, we'd like to avoid
the pitfall of linked files, for example, OLE links on Office documents and
such. Say that we're moving a document from server A to server B and the
document has a link to another document on server A. That other document we also
move to server B. The link in the file is, of course, not updated, and errors
have their wicked way. To prevent this from happening, we'd like to scan the
different volumes for files that have links to other files and get a clear
report. We examined the Link Updater (lu.exe, Quest Software),
but that utility requires you to enter the source and target path of the linked
files and doesn't accept wildcards, so that won't quite do the trick as we don't
know those paths, that's what we're trying to find
out. Anyone who might be able to give a handy pointer in the
right direction for a tool like that ? Thanks in advance, Paul.
|
- RE: [ActiveDir] OT: Linked files. Grillenmeier, Guido
- RE: [ActiveDir] OT: Linked files. Paul van Geldrop
- [ActiveDir] OT: Linked files. Lucia Washaya
- RE: [ActiveDir] OT: Linked files. Lucia Washaya
- RE: [ActiveDir] OT: Linked files. Paul van Geldrop
- RE: [ActiveDir] OT: Linked files. Lucia Washaya
- RE: [ActiveDir] OT: Linked files. Jorge de Almeida Pinto
- RE: [ActiveDir] OT: Linked files. Lucia Washaya
- RE: [ActiveDir] OT: Linked files. Justin_Leney