Administrator’s Guide
229
Using Mirror and Linked Repositories
Promoting mirror repositories
If the machine holding the master repository is unavailable, for example the
machine has suffered a disk crash, you can promote a mirror repository to the
master repository.
Follow these steps to promote a mirror repository to a master repository:
1. In the Management Console’s main menu, click
Tools
, and then click
Repository
.
The Repository dialog box appears, with the Products page showing
(
Figure 8-2 on page 215
).
2. Click the Mirrors tab.
The Mirrors page appears (
Figure 8-3 on page 216
).
3. Right-click the machine shown as the master repository, and choose
Change Master Repository
.
The Change Master Repository dialog box appears.
4. Select the mirror-repository machine from the drop-down list, and click
OK
.
The comment for the previous master repository changes to “Old master
repository.”
Granting access rights
Configuring access to Windows NT mirrors
Access rights must be properly configured for Windows 95 and Windows 98
client machines in order to successfully update from a Windows NT mirror via
the Batch Install method (including updates from login scripts via the update
requester) or the Pull Off Install method.
When you create a new mirror (including the initial master repository) on a
Windows NT machine via the Management Console, it creates two shares: The
first is called REPO$ or REPO (if not hidden), and the second is called
MEUPGD$ or MEUPGD. The REPO$ share contains a copy of all the software
currently installed in the repository; the second share, MEUPGD$, is used to
store Management Edition scripts. Client machines need read access to the
REPO$ share and read/write access to the MEUPGD$ share. The client needs
write access to MEUPGD$ so that it can write the results of an
installation/upgrade back to the share, to be read later by the Management
Console.