svn commit: samba r12695 - in branches/SAMBA_4_0/source/scripting/libjs: .

[Gémes Géza]

Jelmer Vernooij írta:

>-----BEGIN PGP SIGNED MESSAGE-----
>Hash: SHA1
>
>David Collier-Brown wrote:
>  
>
>>Jelmer Vernooij wrote:
>>
>>    
>>
>>>On Wed, Jan 04, 2006 at 09:42:28AM +1100, Andrew Bartlett wrote about
>>>'Re: svn commit: samba r12695 - in
>>>branches/SAMBA_4_0/source/scripting/libjs: .':
>>>
>>>      
>>>
>>>>Does windows allow such a name in 'system -> computer name'?
>>>>        
>>>>
>>>Samba 3 allows it so it is necessary in some cases to have, in order
>>>to have a clean upgrade path.
>>>      
>>>
>>  Is this something that can be detected and optionally corrected
>>in an upgrading script?
>>    
>>
>Yes, it could be detected and corrected. However, we could only fix this
>on the server that is being upgraded - If it is a DC, its domain members
> will break because we can't fix the NetBIOS name remotely. If it is a
>domain member, it won't be able to access its domain later on.
>
>Cheers,
>
>Jelmer
>
>-----BEGIN PGP SIGNATURE-----
>Version: GnuPG v1.4.2 (GNU/Linux)
>Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org
>
>iD8DBQFDu87HPa9Uoh7vUnYRAvLQAKCJrD0c6APYqqn+9vwAXUALDU26rACfUCnW
>/2Sl9NxIUUVBoE7bvwsoiYQ=
>=HX/N
>-----END PGP SIGNATURE-----
>  
>
Just my 2c:
The cleanest way would be to check for that kind of names before doing
any modification, and if any found drop an error message to the admin
explaining the phenomen and giving the steps she/he needs to perform
before a successfull migration and then exit.

Regards,

Geza