Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations gkittelson on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

Client Installation over slow links

Status
Not open for further replies.

Jpoandl

MIS
Jun 23, 2000
2,008
US
Hi,

We have a few client machines that connect via 28.8 connection. This is preventing the installation of SMS to happen because of the link speed. We know that we could modify the SMS logon script so that it installs the client anyway; however, we do not want to hinder the clients (this would be a painfully slow installation.)

Is there any way to create installation diskettes or CD-roms?

Any help would be appreciated....thanks!
 
Hi me, its me again....I found the answer.


SMS has two built-in client installations methods: Logon Installation and Windows NT Remote. We currently use Logon Installation to install most of our client machines. (The only other method we use is a manual SMS client installation.) Window NT Remote installation requires that the client machine is of the Windows NT platform. This method does not require a logon script. Installation happens automatically in the background.

I found this on Swynk.com. Now, this is a program NOT written by Microsoft; however, I've found Swynk.com to be a reliable web site. This utility should get around the 28.8 baud problem.

Another way to install the client is provided by the Back Office Resource Kit:
I found this article on the Microsoft site. It discusses how to PRE-STAGE SMS clients: I cut the important stuff from this technet article to my e-mail:

Pre-install the client core components. Pre-installing the client is beneficial when setting up a client remote from the Systems Management Server Site; for example if you have a contractor build and supply your desktops. When the client is discovered through logon, it looks for some client components locally on the client, and if it does not find them, it copies them from the server. If it does find them, it bypasses copying them at a net bandwidth savings of 6 megabytes per client. To manually pre-stage the client complete the following steps:

Create a %Windir%\MS\SMS\Core\Bin folder.

Rename SLWNT3 (if the client is 32-bit), Slwnt32a.exe (if you are using an Alpha computer), or SLWNT16 (if the client is 16-bit) to Slownet.exe.

Copy the following files in the %windir%\ms\sms\core\bin directory: Boot32WN, Slownet, Clicore, and Snboot.
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top