Mail 伺服器架設

大頭

$ M) e& S& B0 u- x2 a1 H  ]4 K/ n, q9 m
3 K: D4 f5 [7 E6 A9 Q+ O4 L% iMercury/32
3 S1 I! ^$ R* v; b
* f4 _% y+ _& A; A8 Q1 A1 BWhat can a mailserver like Mercury/32 do for me?6 L: }  \, J. i: Q. I2 u$ Q
+ v& l" m. S# O, {7 x
# With a local SMTP server, I can deliver mail without having to use my local ISP's SMTP server. All mail is delivered directly to my recipients mail servers. I'm not bound by anti-spam measures that have been put in place so I can deliver mail completely free of concern about my From headers and which ISP I'm connected to. If a mail delivery is logged as successful then I know that the recipients mailserver has received the message and that it hasn't been lost or delayed in transit.
9 J2 }9 s- G7 q, q7 t7 R7 L# A local POP server allows you to create multiple local POP accounts from which your e-mail client/s may download mail. You can setup your mailserver to download mail from all your remote POP accounts and destribute all this mail to your local POP accounts in whatever way you wish. In this way, you can download all your mail to a single local POP account and then collect all this 'funnelled' mail using a single e-mail account. Even more interestingly, you can get your own domain and with use of free mail forwarding services offered by many domain hosts, create as many e-mail addresses as you like and have messages to all these addresses forwarded/delivered to a single remote POP account. You can then use your local POP server to distribute mail to each of these addresses to their own local POP accounts. Each e-mail address could be for each member of your family or business. Each member can then download mail to their own e-mail clients or accounts. This can save a lot of extra cost associated with paying for multiple remote POP accounts.
$ ~. M0 r( |) @6 H# N9 Q0 V  c4 R% _; a5 `; |0 ^8 D0 d5 N
My intention is to outline, in a simple and easy to understand way, how to quickly configure Mercury/32 for either POP or SMTP services or both. The beauty of Mercury/32 is that it's modular so you can run only those services you want to. Mercury/32 is just a 1.5MB download and uses little system resources. It's compatible with all Win32 Windows versions. The following two documents outline how to configure your own POP and SMTP services using Mercury/32:# B1 G1 B( T' t: I2 g6 x1 q

. A- e# p1 O; S7 e! N    * How to configure Mercury/32 for POP services.
: `/ M, l8 r. L* u8 ^# j7 u    * How to configure Mercury/32 for SMTP services. 7 N, K& f9 D- k; R! I
  Y3 t* T3 `5 v  c
Once you're done with that, it would be useful to have your mail services start at boot-time.. V. d8 c4 d/ I, }7 _' y# r) c; M) l2 E

7 v. F% i; ~/ p5 V4 b    Auto-starting Mercury/32 at boot time
8 D  Y$ b: t! k4 r* s2 p: y9 u9 c! ?; |7 |8 P5 ?2 l# i
    To auto-start Mercury when your system boots, you'll need to create a shortcut in your system start up folder, for the Mercury Loader, using the '-m' parameter. For example, 'C:Mercuryloader.exe -m'. The '-m' parameter will minimize Mercury/32 on startup.
, {  s+ R; r3 [1 y+ Q# @    Running Mercury/32 as a service3 P' r! t* m7 q/ F8 J

! }: S+ _% t$ Q+ Q' q4 ^7 U    If you wish to run Mercury/32 as a service there is no direct support for this in Mercury. However, this is still possible. For instructions on how to achieve this you can read the following articles:
) [; }5 w. n8 Z+ L6 X3 R- l  p: O! k2 E( S$ n. o
        * How to Run Mercury as an NT Service* Q; a% c" A- f
        * How To Create a User-Defined Service under NT
+ V& O" ^4 p0 i% K* l. H0 a- r' b) c& t, W. c
    The files that you'll need to create an NT Service as discussed in the above links may be downloaded here.
+ S; B. j8 u# A. e& g% m8 F: z+ N7 o* C+ ?0 ^6 {$ @
    There's also the application/utility AtYourService, that will turn any DOS, Windows, Java application as well as batch file into a native Windows NT/2k/XP service. It's not freeware though.

labman

Setting up Mercury/32 as your local POP server
: L0 h% Q1 z1 N8 S
5 [2 ?7 }4 O7 n- c; ALet us go over the modules required for running Mercury/32 as a POP server
- [2 F: Y8 A% @# t# MercuryP (POP Server Module) - This module allows you to retrieve mail without having having physical access to the drive on which the mail is stored. MercuryP presents a list of new mail messages to the POP3 client and it's this module that your local e-mail client will interact. Proper configuration of this module is critical to your successfully retrieving mail from Mercury/32.
6 p" O% x/ n, Z  u
: X# Y( Y* C$ ?& K4 H; b( {# l8 N$ Q. ~, x. y
# MercuryD (POP3 Client Module) - MercuryD allows you to retrieve mail from as many remote POP servers as you wish and to, and distribute that mail to users on your local system or network.5 I8 F% q- \8 s- `
8 k" }) U2 ^1 t6 q: G, ^. A* L
; N/ o+ n+ R- _  x
# Mercury Core Module - This module is always needed by Mercury to function as an SMTP or POP Server
! w2 y, S8 E' I) I" dStep by Step Configuration for POP Services
& [1 D/ q9 o' `+ @* Q1 j2 m  s$ t% G& P2 ]# ~
In Mercury, go to the Configuration menu and see if the required modules are active, i.e., not greyed out. If any of the required modules are greyed out then you can activate them by going to the menu item, Configuration/Protocol Modules and enabling MercuryP and MercuryD. You'll then need to exit and restart Mercury so that the modules are initialized. You now have POP server services.
+ m/ ^4 a2 C. D9 R) t0 e0 P8 g+ jCreating Local POP accounts
5 A) j# S* }( X
5 h$ E# Y, _1 HGo to Configuration/Manage Local Users. There, you can create the local POP accounts. The username is the name of the POP account, for example 'jasper' as illustrated in the captured image below. You'll use these usernames and the passwords you defined, as the credentials for configuring the POP account options in TB!. Of course the POP Server in TB! will be 127.0.0.1 or localhost., w9 q1 t3 ?1 P
2 v: V+ u+ L; k4 D

7 F8 q3 i  L, \: l0 n6 L3 Z# W; ?- \8 y3 m; e7 f+ e
MercuryD Configuration
# L+ ^5 L( T6 l+ L; F
0 \) Q# g. ~7 o8 i$ MConfiguration/MercuryD will take you to the configuration panel to configure the remote POP servers that Mercury should download mail from. Use the add button to add a remote POP server to download mail from. For 'Local user' you put the local POP account you wish the mail to be placed. Default account is the account you wish mail that Mercury doesn't know what to do with, to be placed. You can define the same account. An example is illustrated in the capture below.
/ M% d" o. d4 A! \" nMercury D Configuration/ x& Y1 y, |$ X6 o# [, ]9 v! s
9 X  n9 J# e% d1 {2 r) |' ]
9 `) r6 p- [0 }& \6 p- B
Aliases. O! N9 |' G* @( f; c5 B3 `# ?

& T3 X& e- {* q3 \- sAnother aspect of the configuration is defining your Aliases (Configuration/Aliases). What these basically do is to tell Mercury that mail to a particular address belongs to local POP account x. You should define an alias for all your e-mail addresses. Note that the alias is the e-mail address and the real address is the POP account in which the mail for that address should be placed. An example is illustrated in the capture below., V. h* X# ?4 V% X# B8 `5 B1 A
Configuring Aliases
5 q" _1 J& b! _2 G
5 G5 X+ Y4 C0 k  j8 sMercuryP Configuration
8 e1 I* X: [7 c: z( y7 I5 L4 D! q5 [. @
. O# X# \  `' k$ U6 ?- D0 e9 EYou need to configure MercuryP so that Mercury will accept connections for mail delivery, from your own machine, or any other machine on your network(if you're on one). Go to Configuration/MercuryP. At the bottom of the panel is 'Connection Control'. Hit the add button and put 127.0.0.1 as the IP address and enable 'allow connections to the address book group'. (See capture below)., W/ Y+ z9 u4 @$ M
Mercury P Configuration8 M% O- o/ h6 ^. B

" f( M. n, X/ {3 d+ I- m2 ~/ R# p5 ^0 D- q- w
The Mercury Core Module
9 n6 J9 M$ P, d* `+ T
. }  x8 J; z7 e( e3 ?# A* K% U# ]( {Open it's options and configure Mercury to handle internal deliveries. You need to tell it which domains are to be treated as local so that any mail addressed to someone with that domain address will be locally delivered. Add any domains you may own here, for example, 'jaspernet.com'. (See capture below) It's this setting and your alias settings that will effect proper local deliveries.
3 B- |- @+ T+ D& e$ X: _" [5 O7 f, ?Core Configuration2 @3 |; C6 d. g, {( s! @& e; d

% c% p/ K! j/ U$ Q3 `- L' E* e4 y; b6 m8 g) I2 I1 }% w
This should now give you a working POP Server setup

labman

Setting up Mercury/32 as your local SMTP server6 X/ P: H* N- R& H/ A! Q& l
1 `5 q' R; t* j" t& g
More and more users manage their e-mail using multiple POP accounts and multiple ISP accounts. At the same time, spamming is also a serious problem and security measures are in place to make it not so easy for spammers to do the evil that they do. One of these measures, is to prevent relaying of e-mail through ISP SMTP servers for which you don't have an account. Ways to prevent unauthorized relaying include the checking of your message From header information for a valid address for the ISP's domain. Another is through the implementation of POP before SMTP. The long and short of it is that it becomes impossible or miserable for many dialup users to manage mail using a single ISP SMTP server. One way of getting yourself out of this misery and inconvenience is to run your own SMTP server.
. Q0 `0 @! R) P. y8 T% {' i% E
" R3 ?/ v+ U- I  Z- P3 MLet's go through the modules that are needed in order to set up Mercury/32 for SMTP services:
9 _. I7 o4 q$ d0 p. Z# Mercury Core Module - This module is needed for Mercury to work, so this must be installed.! A3 I; F- N/ a8 d6 I4 c
# MercuryS (The Mercury SMTP Server Module) - This module is what listens for incoming SMTP connections and accepts incoming mail either locally (in this case your e-mail client) or remotely from another machine and then places the mail in the Mercury Spooler for processing. Proper configuration of this module is critical for your e-mail client to interact and successfully transfer mail to the Mercury Spooler.
. V, d" j: A& o+ Q" R0 r+ X
' x9 R' ^. x2 B$ U# Z2 QYou now have to choose between running one of the two following modules, depending on your needs. You cannot run both of them at the same time.: {/ Z3 q& }0 M1 B' E. n/ _
# MercuryE (Full SMTP delivery client) - This module is what will deliver your mail directly to the remote SMTP server. MercuryE completely bypasses your ISP's SMTP server and carries out a direct delivery of e-mail. All you need to do is provide it with a valid nameserver to carry out the DNS lookups for the domain names for each recipient address and it will do the rest.% B8 U! y" d/ q( ?
# MercuryC (SMTP Relay Client) - This module will relay your e-mail to an SMTP server that you designate as a SmartHost. This can be one of your ISP SMTP servers. This module is useful if you're using a dialup connection and are concerned about the time being spent doing direct mail deliveries with MercuryE, when mail could be delivered more quickly to your local ISP's SMTP server.- G' w2 J1 R; J6 ~( `

" Q0 v7 ?9 X6 b: ^/ v' LWhile installing Mercury/32, you'll be asked which modules you wish to use. You can now select the ones you need to use." @% _9 P1 m5 r/ E

5 u+ L5 |* q9 N4 ^- {Let's now go into the actual configuration of the modules. I'll only mention those critical options that must be properly configured to get yourself up and running. You may then, at your leisure, read the documentation for information on the other options:
: H: s/ S, v2 a8 ?. h" B" l% MThe Mercury Core Module
' X; z# I/ _2 r* h2 ~( P& z8 h- q, N' K: q& q3 |5 x- Q
These configuration options may largely be left unchanged if your interest is only in SMTP services.  @$ p8 h7 k  U; Y1 v
5 r! _( t* F6 G: Z5 W/ u8 Z
Under the 'General' tab in the mercury core module configuration pane, there are two important settings. The internet name for your system should be a qualified domain name. If you have your own domain, you can enter it here. If not, then use the domain name for your favourite ISP, for eg., aol.com. The other important setting is the postmaster username. You should set this to 'admin'. (see capture below) Error messages and notifications need to be sent to an account and the Mercury admin account is automatically created for this.
% Q- J: Y( x* t2 q. aMercury Core Module Configuration
: C8 I/ j; C4 H
3 A: c& c9 }9 q; N+ ^7 i: N& H* w% r# ^' S; t% u" ]" @
You can setup your e-mail client to intermittently download mail from this account so that you can get these error messages. To do this make make your POP server 'localhost', the username admin and the password blank.+ ]9 M2 i) G: b1 K! g. d
The MercuryS Module
9 M0 Z( [$ G  s4 x7 ^
8 z; Z3 W) D& e# r3 W" N2 t7 lUnder the General tab, use the same domain name as you used for your internet name in the mercury core module as the name to announce yourself as. Also, enable the option 'accept mail for invalid local addresses' as shown in the capture. This will make MercuryS accept mail from any e-mail address you may wish to use.
& x/ L4 ~4 P* }  M, i( sMercuryS Configuration" K; `& O: M  J7 V/ A4 S
7 S' c, @: a' C" r" W

- W  p, H- f" J  h# ]4 S! ]Now go to the 'Relay/Connection Control' tab. Here, you need to include your machine as one that is allowed relay privileges. If Mercury/32 is installed on your machine, you give Mercury your local IP address, i.e., 127.0.0.1 . So hit the 'add restriction' button and enter the IP as shown in the capture. Enable 'allow connections from this address group' and hit OK.
3 X1 }0 `7 n& L) H! y- D- n: M. NRelay Configuration
1 a) I) {8 I: Q- V" D9 Y/ H
) v* O2 S) A+ T: s* f
1 k) v8 A( _( |, GAlso enable the option 'Do not permit SMTP relaying of non-local mail'.
6 C- a& Q) p+ v- iThe MercuryE Module1 s- ^1 a5 |' |. I

. f' V6 W, d  MThis module will directly deliver mail for you, so it needs to be given the IP addresses of nameservers to use for resolving the domain names of e-mail addresses. If the machine that you've installed Mercury/32 on is on a network and doesn't get a direct connection to the internet, you have to include your ISP nameservers as I've done in the capture. Otherwise, you could just leave it blank and the nameservers defined in the network control panel will be used instead. You can also specify how often the module should check for mail to be sent, as well as the server timeout.% H2 D  c& \( a# I
1 ?; f6 A3 ]9 w  E
If you need to include your ISP nameservers and you don't know the IP address/es, then you can find this out by either looking at your TCP/IP's DNS configuration (this is in your network configuration panel) and taking the IP's from there, by running a Whois search on your ISP's domain, or for NT users, running the command 'IPConfig /all' and taking the DNS information from there. As a last alternative just call your ISP and ask. :-)
/ c7 R: w( m9 b! O( BMercuryE Configuration
0 A6 B/ L+ C6 v7 y2 `- S% U% d9 f$ ]) `. d4 J9 w$ Z
The MercuryC Module
( F$ ]2 h3 i+ l" c7 p. t) N( O$ R# K6 N# x8 g7 N8 g8 K
This module will send your mail via a SmartHost, so the configuration here will involve filling in the information on the remote SMTP server you wish to use as the host. As you can see from the capture below, the options are straight forward.
7 I. Z& J, I9 tCore Configuration
' F$ I7 d6 P, |1 A1 q! |: w
& z$ |- h( \/ E- W, k: w" x/ C' O; F# v$ P8 `- \, t
Mercury/32 should now be ready for SMTP services. The only thing left to do would be to configure your e-mail client to use Mercury/32 for SMTP services. To do this simply put 'localhost' or '127.0.0.1' as the SMTP server.

labman

Running Mercury/32 as an NT Service
# \* P2 R1 k( k7 G; m: F/ w9 y& o5 K& x8 |- {: g. |5 O
Q: I want to run Mercury/32 as an NT Service at startup. How do I do this?
8 h, M' s% x1 o: z, M
9 ~3 b0 ~( [+ {( Z; m7 I; bA: As of this writing, Mercury/32 (currently v3.21c) does not directly provide an option for running as a service. However, you can use the MS SRVANY utility from the Windows NT Resource Kit (ftp://ftp.microsoft.com/bussys/winnt/winnt-public/reskit/nt40/) in order to make Mercury/32 run as an NT Service. Here is a summary of the steps:! c" ~; T1 K- J2 r+ p/ n8 }6 z: ^

# D, {. o# s; a4 i0 U  N   1. Obtain a copy of SRVANY.EXE and its supporting files and copy SRVANY.EXE to the WinNT SYSTEM32 sub-directory (for this discussion, we'll assume that directory is c:\winnt\system32).
% d; p5 V' V! h! ?$ O2 Z6 }       * `, X2 N+ M5 q
   2. Type: INSTSRV Mercury32 c:\winnt\system32\srvany.exe
1 }# y2 D, f$ w: _, ?      This step adds a service called Mercury32, which will use the srvany utility to control the Mercury/32 application program.
4 P6 \$ Q, t% R( k6 h0 u      There is also a GUI version of INSTSRV (called SRVINSTW.exe) which will walk you through the above step, if you prefer.- }9 G) Y- n- \9 w+ j' o# d& e
      
- L* E) o$ ^; t, _   3. Run the registry editor (Regedit.exe) and add a "Parameters" key to the Mercury32 service under the following location:
! m, @8 }- M: _, _! V5 B      HKLM\System\Current Control Set\Services\Mercury32
2 y, Y+ s; \' y: ^3 A* i      Within this new key (HKLM\System\Current Control Set\Services\Mercury32\Parameters), add a value of type REG_SZ called "Application".; W. P6 u# ~4 }# |1 v% F
      The value of this string should be the full path to the Mercury.exe application.1 x# O! e( @5 `% o
      ie: "d:\mercury\mercury.exe"
, a& V) ~0 ~- b$ S8 E! N       5 z9 ?0 p2 w$ F: C
   4. Open the Services icon within the Windows Control Panel and check the "Allow interact with desktop" checkbox for the Mercury32 service, then try starting it.; ?, O& T: D2 i1 H
       ; z' H- I$ ?" q* I3 q
" s8 j9 f# V& A+ w& [2 O0 g
The above procedure is documented in the SRVANY.WRI file if the above instructions are not clear enough.  H+ v8 p! d) h

: M  O) T# i+ G% D: nWARNING! Mercury/32 only saves it's settings when you close the Mercury/32 application. If Mercury/32 crashes or the PC crashes, any changes you made to Mercury/32 since you last started it will not have been saved.
+ A" f1 X' N& h* G  o9 ^7 D
+ l5 C8 ?8 G: m' v6 _1 N( jKeeping the above warning in mind and the fact that Mercury/32 is not a true service, you should never shut down Mercury/32 by just stopping the Mercury/32 service from within the Services control panel applet. If you need to shut down the Mercury/32 service, you should first close Mercury/32's own application window (File -> Exit menu option) before shutting down the Mercury/32 service entry within the Services control panel applet. You can then start Mercury/32 again from the Services control panel applet, if you wish.: e. b% Y# i' P3 ]$ A
3 A3 A1 l3 y/ ~! D8 Z
Some sites have also reported success using FireDaemon for WinNT/2K/XP (http://www.firedaemon.com/) to run Mercury/32 as a service under WinNT/2K/XP.

labman

Windows NT Resource Kit 提供兩個公用程式，讓您能為 Windows NT 應用程式和某些 16 位元應用程式 (但不含批次檔) 建立 Windows NT 使用者自訂服務。
8 K3 |, h4 \# B9 F
% t1 K$ ?# K3 ~/ ^9 r( z, DInstrsrv.exe 會從 Windows NT 安裝及移除系統服務，而 Srvany.exe 則可讓任何 Windows NT 應用程式執行做為服務。
2 e7 d# h% H* A- M
( ^+ O: q2 {3 p! r. w9 M) ^! j
, M5 ?  e1 P: T( A9 z8 p如果要建立 Windows NT 使用者自訂服務，請執行下列步驟：
- ^' V+ v) b+ [5 W, Q" b$ z* J# H3 N" Y  u
   1. 在 MS-DOS 命令提示字元中 (執行 CMD.EXE)，輸入下列命令：
5 h% ?7 ~# }4 ?& k' C
$ H, v1 x; @  u* q: J7 O      path\INSTSRV.EXE My Service path\SRVANY.EXE
5 Z7 S  ]1 F' n0 v
. b& o! E8 V$ Y* ~; K5 X      其中 path 是 Windows NT Resource Kit (即 C:\RESKIT) 的磁碟機和目錄，而 My Service 是所要建立的服務的名稱。* r' [+ V+ p% X+ K5 P8 V$ C
9 y( y. s& L8 N9 p, O
      範例：
* ~2 \6 M, [9 H# k# c9 X      C:\Program Files\Resource Kit\Instsrv.exe Notepad C:\Program Files\Resource Kit\Srvany.exe
+ `! L. M- h4 @% G. _. U/ _% f      注意： 如果要確認服務的建立是否正確，請檢查登錄以確認4 P! w" W& d/ p- U! Y; j
      HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\service name+ i+ o+ `4 ]) s, Y8 ?" m1 Q
      下的 ImagePath 值是設定為指向 SRVANY.EXE。如果設定不正確，服務在開始之後很快就會停止，並傳回事件識別碼 7000「service name 無法啟動」。
. ^, p8 S* p6 M6 j- ]  Z* G" X$ q! w: h6 b4 t! g
      警告：不當使用「登錄編輯程式」可能會導致嚴重的問題，甚至必須重新安裝作業系統。Microsoft 不保證可以解決您不當使用「登錄編輯程式」所導致的問題。請自行承擔使用「登錄編輯程式」的一切風險。
2 b1 U5 l' x2 u% C/ p
+ m5 v' t- ?( ^$ d' L! v+ |      如需有關如何編輯登錄的資訊，請參閱「登錄編輯程式」中的「變更機碼及值」線上說明主題或「新增及刪除登錄中的資訊」和「編輯登錄資料」線上說明主題。( n7 ]1 P9 O! U
1 R) U1 l  H, |9 a( L% y; M
      注意：在編輯登錄之前應該先加以備份。
2 \9 n4 v) l9 _  K9 ]) Q   2. 執行「登錄編輯程式」(Regedt32.exe) 並找出下列子機碼：
. E5 [( V! U" o0 h: O. p, w6 e& G: f( b7 G
      HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\<My Service>
' [: b8 l  D8 l% j$ o( C   3. 在 [編輯] 功能表上，按一下 [新增機碼]。輸入下列資料並按一下 [確定]：
, c. E% M  C# ?8 I9 g9 E6 J; j+ T2 }, }* r7 W8 S' W; p  n. ^
      機碼名稱：Parameters% {; n3 c: h! s- m) w9 M9 L
      類別：<保留空白>
" P* W1 t& n; o   4. 選取 Parameters 機碼。6 p7 r" V9 d' j2 p+ ~8 T
   5. 在 [編輯] 功能表上，按一下 [新增值]。輸入下列資料並按一下 [確定]：
- P9 X) c3 U+ p' {3 W) i: U. ?  }: J0 [% G/ y5 b9 J
      數值名稱：Application6 z2 x3 `# I. s0 P. `  P
      資料類型：REG_SZ
) J0 O: X8 _1 P$ @; k      字串：<path>\<application.ext>4 s6 S1 y; g% e5 o! E; x
+ [3 R& s1 v9 q- b' q; }, l( ^
      其中 <path>\<application.ext> 是磁碟機與應用程式可執行檔的完整路徑 (包括副檔名，即 C:\WinNT\Notepad.exe)
) ~7 D) Z* X1 d& R2 u   6. 關閉 [登錄編輯程式]。
0 g2 ~$ ~7 b) Z: m/ ?% _7 m" B7 }% B+ U. Q# s
依據預設，新建立的服務會設定為在系統重新啟動時「自動」執行。如果要將此設定變更為「手動」，請從 [控制台] 執行 [服務] 小程式，並將「啟動」值變更為「手動」。設定為「手動」的服務可以使用下列其中一種方式啟動：
; n; \8 [' r0 H# `- 從 [控制台] 的 [服務] 小程式' S) _+ J( q+ p& c. `
, y' V# q3 x9 H+ h1 W  w
- 從 MS-DOS 命令提示字元輸入：
+ X6 M! a; k* M2 D# y- o) s
; }* G. m# _2 U) \9 J6 I" DNET START <My Service>* c5 k9 I- [: @) C2 I7 o

! d2 c5 [# Q; _8 C$ N- 從 Resource Kit 使用 Sc.exe 公用程式從 MS-DOS 命令提示字元輸入：" R1 k% F! r7 p, j- h, _0 c! A
( u" [& D( i) ]- H0 F" T: G; ]
<path>\Sc.exe start <My Service>
( l0 H" n" h4 J6 J+ |, C, e6 @1 h# w$ L/ N. K
其中 <path> 是 Windows NT Resource Kit 的磁碟機和目錄 (即 C:\Reskit)。
0 h7 g' e3 n$ s+ l7 \$ a
5 d5 |2 B0 q5 u  t7 ?
& n$ U4 \8 b. H/ L6 p如需安裝與移除使用者自訂服務的詳細資訊，請參閱 Windows NT Resource Kit 公用程式所附的 Srvany.wri 文件 (即 C:\Reskit\Srvany.wri)。這份文件也可以在 Windows NT Resource Kit 光碟的 Common\Config 目錄中找到。