Windows NT/AD Migration to OES on Linux and NetWare®

Bruce Cutler, Senior Software Engineer

Novell, Inc

Margee Meyer, IT/IS Manager

Fairchild Semiconductor

Jeff Marden

Fairchild Semiconductor

Overview

Bruce Cutler

Migrate to OES on Linux

Native (Microsoft client)

NCP (Novell client)

Tools

Margee Meyer and Jeff Marden

Migrating from Windows AD to NetWare

Fairchild Semi-Conductor migration

Bruce Cutler
NT to OES on Linux

Client access and management overview

Migration tools discussion

ACL's under-the-covers

Linux User Management

OES/Linux Install settings

Where are you now?

All Microsoft

NT Domains

Active Directory

Mixed – Microsoft and NetWare

All NetWare – then why are you here?

Windows

NetWare

Mixed

Why do you want to migrate?

Linux - Lower cost for hardware and software

Secure – no more daily Microsoft Security updates

eDirectory™ - Easier to manage than multiple domains

Choice – not tied to one vendor

Collaboration - Exchange your Exchange to GroupWise®

Support - Best technical support from Novell

The Future – Linux and Novell

OES =
Managed Services for the Enterprise

Open Enterprise Server

SUSE LINUX Enterprise Server

+

Identity Management - eDirectory

Central management - iManager™

Enterprise-wide health monitor

Files systems with rich ACLs

Multiple client protocol support

Migration tools

Distributed, scalable printing

User Access, Management metholodogies

How do you want to access a manage?

NCP-based = Novell client, OES Tools = iManager, SMB-based = Microsoft client, Windows tools = Windows Explorer

1

2

3

Access/Managment method

User Access: NCP-based

Management: OES tools

User Access: SMB-based

Management: OES tools

User Access: SMB-based

Management: Windows tools

User Access: NCP and SMB

Management: OES and Windows

4

NetWare

Some NetWare/Windows

Some NetWare/Windows

Some Full Windows

All NetWare/Windows

All Full Windows

Source Environments

Method

Method 1 NCP client, OES management

File System

NSS volume (no meta-data loss)

Reiser/NCP volume (meta-data loss)

Server Consolidation Utility

Copy NT users and groups

Copy file data

Manage via iManager, ConsoleOne

Access via Novell Client

Install NCP modules

Client

Use Novell client

Method 2 SMB client, OES management

File System

Same as for Method 1

Install and configure Samba

Set up shares

Manage rights via iManager or ConsoleOne

User can't manage rights

Server Consolidation Utility

Same as for Method 1

Access via SMB

Mapped drives as with Windows NT/AD

Method 3 SMB client, SMB management

File System

Reiser

Install and configure Samba

Set up shares

Manage rights via Windows Explorer

User can manage right

Copy users and groups

Run Vampire from Linux machine

Copy file data

Xcopy from Windows 2000/XP machine

Command-line utility

Method 4 SMB and OES client and management

Requirements:

Enhanced Virtual File System

Enhanced Samba

All identity objects managed by eDirectory

Files managed by NSS

Open Source Effort – Novell not in control but in cooperation

Migration Tools

Samba

Vampire

Xcopy

Beyond Compare

Server Consolidation Utility

Disclaimer goes here about third party tools

Samba

SMB access (that's where the name came from)

NT Domain Emulation on Linux

Open Source Project

Novell Samba – eDirectory back-end

Vampire

Part of Samba

Sucks the lifeblood (thus the name) out of NT domains

Users

Groups

(No selection)

(Doesn't handle file data)

Puts data into Samba database

Command-line utility

Runs on the Linux box

Xcopy

Part of Windows 2000/XP

Copies the file data

Lots of options

/x – copies ownership and ACLs (DACLs)

/o – copies file audit and system (SACLs)

Runs on Windows 2000/XP

(Scopy – predecessor supported on Windows NT)

Server Consolidation Utility (SCU)

Drag and drop

NT Domain (for everyone permissions)

Users (either as a group or individually)

Groups (either as a group or individually)

Folders

Create

OU's

Folders

Template object

Home Directory

Other properties

SCU - Object data

NT to eDir Users

Passwords

Imported if you can export them

Random

Same

Apply template

Additional properties, including home directory

NT to eDir Groups

Local groups to eDir groups

Global – only used for domain trusts

Recommend converting to container permissions

SCU - File data

NT Domain Info

Everyone permission

Folders and files

Permissions

Owners

Attributes

SCU - Server Connection Issues

To Linux

Push – source pushes data to destination

Hosts file or SLP configured on the source

NetWare

Pull – destination pulls data from source

Hosts file or SLP configured on the destination

NetWare

OES Linux

NetWare

OES NetWare

PUSH

PULL

3

Other SCU Issues

Connection issues

servers must be able to see each other

Speed issues

communication medium as far as possible

1

2

4

Permissions (ACLs) Under-the-covers

Samba vs. NCP vs. NSS Volumes

Samba

Extended attributes on the files

NCP volume (Reiser, ext3 etc.)

Stores trustees on xml file

All files owned by root

Only accessible via Novell client

NSS volume

Permissions passed on via VFS to native FS

XYZ

Samba

Permissions

ABC

Permissions

XYZ

ABC

NCP

Permissions

XYZ

ABC

NSS

NSS Black Box

Extended Attributes

Trustee.XML

LUM Enablement

Linux User Manager = LUM

How?

eDirectory Linux workstations

eDirectory LUM Groups

eDirectory Users

Sales Workstation Object

ABC Group

Sales.Novell

eDirectory

Sales Linux Box

Joe

Pete

Sales Dept.

Sales Dept. Server

Joe

Pete

Linux User Management

Linux User Manager = LUM

NSS volumes only

Required for:

user space restrictions

native file access

Linux user enablement setup

Options

Only matched-up users

or

Container for group for each Linux server

Container of users

Specific users

or

Both

OR

OR

Linux Install Dependencies

Recommended OES products to install:

eDirectory	(always)

NCP server	(always)

NSS	(if going to NSS)

Backup	(SMS - always)

LUM	(always)

Samba	(if SMB access desired)

SCU Futures (For Windows source)

Integrate Vampire and Xcopy functionality

Active Directory migration

Migrate more services

Email (Exchange to GroupWise)

Workgroup databases to MySql

Web services

Printing

Margee Meyer
NT Domains to NetWare

NT Domains to eDirectory

Environment

AD or eDir (WHY)

Issues

Migration with SCU

Results

Environment

15 Sites World Wide

200 to 1000 Users per site

2000 Laptops

Many Remote from any Office

Manufacturing PCs (tools)

Frame Relay WAN

Hub back to Corporate

Fairchild Semiconductor
wide area network overlook (1/2005)

Sungard Backup/Recovery

Singapore

QT

Carlsbad

California

Stuttgart

Germany

Guadalajara

Mexico

Saddlebrook

NJ

AT&T Global Network MPLS Transport Network

Cebu

Philippines

Swindon

UK

Salt Lake City

Utah

San Jose

California

Mountaintop

PA

Colorado Springs

Colorado

Singapore

Suntec

Penang

Fairchild Headquarters

Portland ME

Suzhou

China

Hong Kong

Furstenfeldbruck

Germany

Paltan

Korea

Suwon

Korea

North Branch

NJ

Irving

Texas

Loveland

Colorado

Melbourne

Florida

Portland ME

Running Hill

Chippac

Malaysia

Osaka

Japan

Tokyo

Japan

Internet VPN Connections

Paris, France

Milan, Italy

Stockholm, Sweden

Chicago, Illinois

Lansdale, PA

Houston, Texas

Farmington Hills, MI

Qing Dao, China

Andover, MA

Executive Homes

Austin, Texas

Helsinki, Finland

Equant

IP Global Network

MPLS

Transport Network

Shenzen, China

Beijing Sales

Taipei, Taiwan

Shanghai, China

Singapore

Shawhouse

Beijing Design

Problem/Issues/Requirements

Disparate system Directories

No Centralized IS/password management

Difficulties in sharing files

Traveling users difficult to print within sites

8 Directory structures – Too many different ways

No Centralized Management

Patches

Updates

Application Delivery

Novell Sites only 30% ZEN tools

60/40 eDirectory/domain

AD or eDirectory

1

2

3

3rd Party Review

eDirectory

AD

Mixed (eDir/AD)

AD would have required double size of WAN pipes

Larger percent of servers needed for catalog servers

AD/eDir No reduction in Administration world wide

ZEN tools

Edir/Novell was right answer

Clustered Servers with ZEN tools

Central Administration

No WAN increase

Reduction of Admins (10% first year)

Why eDirectory & Novell

Migration with SCU

Each Site had a stand alone NT Domain or AD Tree

Build Netware Cluster

Using SCU Migrated Users & Home Dirs

Required OUs to be built

User Template per OU

Client Migration

Novell Client Distribution

Web link with ACU and unattend.txt

LANGaurd with self extracting file

Login Scripts

Base Login Script to Home/Group/App drives

NT Domain Script to Win Shares until fully migrated

Created auto Win ID/Password in script to allow pass thru

Client Migration

Login Script used to Deploy ZEN agent

ZEN Benefits

DLU Policy to remove dependency on Win SID @ PC

Users logon to Novell – no issue with local SID

Policy on User rights at system, User vs. Admin

iPrint Deployment

Web

Migation Issues

Windows Profiles Local & Win Server

Roaming Profile migration issues.

Open File issue when saving Profile – difficulty moving

SIDs

Emp Ids to User Names

Next Steps

Increase use of ZEN

application distribution

imaging

inventory

security management (SOX)

dirxml and LDAP authentication

nsure auditing

Citrix integration

Questions

Server Consolidation Utility

Windows Workstation

SAMBA

NCP

ACL, etc.

NW Trustee

VFS

NSS Events

NSS

Reiser, ext2, etc.

NW Trustee

file

flat file at root, hidden

Extended Attributes

Kept in Sync

Has set access controls

Mapped to Samba share

2003-12-08T12:43:39