Sunday, August 28, 2005
Image-Based Windows XP Deployment: "http://www.microsoft.com/windowsxp/pro/techinfo/deployment/activation/default.asp"
Thursday, August 25, 2005
Monday, August 15, 2005
Thursday, August 11, 2005
Monday, August 08, 2005
Altiris Blog Site: "[network.setup]
version=0x3110
netcard=GEN_NDIS,1,GEN_NDIS,1
transport=tcpip,TCPIP
lana0=GEN_NDIS,1,tcpip
[GEN_NDIS]
drivername=UNDIS$
[protman]
drivername=PROTMAN$
PRIORITY=MS$NDISHLP
[TCPIP]
tcpwindowsize=11600
NBSessions=1
DisableDHCP= 0
drivername=TCPIP$
BINDINGS=GEN_NDIS
LANABASE=0
[pktdrv]
drivername=pktdrv$
BINDINGS=GEN_NDIS
intvec=0x60
chainvec=0x66
novell=no
-----------------------------------------------------------------------------------------------
and your tcputils.ini will look like this:
tcputils.ini
-----------------------------------------------------------------------------------------------
[tcpglobal]
drivername=GLOBAL$
[sockets]
drivername=SOCKETS$
bindings=TCPIP_XIF
numsockets=1
numthreads=32
poolsize=3200
maxsendsize=1024
[telnet]
drivername=TELNET$
bindings=TCPIP_XIF
nsessions=0
max_out_sends=0
-----------------------------------------------------------------------------------------------
If Tiny RFC fails to load and gives an insufficient memory error, then reduce the tcpwindowsize down to the next smallest size in the above list.
Also, do not increase the NBSessions=n or the numsockets=n to a number greater than you really need. The larger the number of connections you place in these two entries the smaller the tcpwindowsize needs to be as each server connection added uses memory, reducing the maximum tcpwindowsize pro-rata."
version=0x3110
netcard=GEN_NDIS,1,GEN_NDIS,1
transport=tcpip,TCPIP
lana0=GEN_NDIS,1,tcpip
[GEN_NDIS]
drivername=UNDIS$
[protman]
drivername=PROTMAN$
PRIORITY=MS$NDISHLP
[TCPIP]
tcpwindowsize=11600
NBSessions=1
DisableDHCP= 0
drivername=TCPIP$
BINDINGS=GEN_NDIS
LANABASE=0
[pktdrv]
drivername=pktdrv$
BINDINGS=GEN_NDIS
intvec=0x60
chainvec=0x66
novell=no
-----------------------------------------------------------------------------------------------
and your tcputils.ini will look like this:
tcputils.ini
-----------------------------------------------------------------------------------------------
[tcpglobal]
drivername=GLOBAL$
[sockets]
drivername=SOCKETS$
bindings=TCPIP_XIF
numsockets=1
numthreads=32
poolsize=3200
maxsendsize=1024
[telnet]
drivername=TELNET$
bindings=TCPIP_XIF
nsessions=0
max_out_sends=0
-----------------------------------------------------------------------------------------------
If Tiny RFC fails to load and gives an insufficient memory error, then reduce the tcpwindowsize down to the next smallest size in the above list.
Also, do not increase the NBSessions=n or the numsockets=n to a number greater than you really need. The larger the number of connections you place in these two entries the smaller the tcpwindowsize needs to be as each server connection added uses memory, reducing the maximum tcpwindowsize pro-rata."
Altiris Blog Site: "Increasing imaging speed
Increasing imaging speed
--------------------------------------------------------------------------------
OK, the Protocol.ini and the tcputils.ini files are located in the net folder for the various NIC's found in the Bootworks Configuration utility.
The tcpwindow size is defined by the number of servers you are connecting to from your client durring PXE boot. So if you have a Deployment Server and your images are then located on a separate file server you would be connecting to 2 servers in DOS Therefore you would need to enter a tcp windowsize=8700. You may wish to experiment with this a bit as it can be variable depending on the NIC you have on the client and also if you are using UNDI drivers or the correct DOS NIC driver. The tcpwindowsize must be specified in the [tcp] section of the protocol.ini
So the tcpwindowsize is as follows:
for 1 server tcpwindowsize= 11600
or tcpwindowsize= 10150
for 2 servers tcpwindowsize= 8700
for 3 server tcpwindowsize= 5800
for 4 server tcpwindowsize= 4350
for 5 server tcpwindowsize= 2900
for 6 server tcpwindowsize= 1450
The nbsessions setting is already in the protocol.ini and should simply be changed from the current number to the number of servers you are connecting to, which in the above example is 2 (a Deployment Server and a File Server). This setting also appears in the [tcp] section of the protocol.ini
numsockets is an entry which appears in the tcputils.ini file under the [Sockets] section and again should be changed to the number of servers, ie in this example 2.
You protocol.ini would now look a bit like this (note this is for the UNDI driver set and the rest of the configuration should NOT be changed to match this example, I have just included it for completeness):
Protocol.ini
------------"
Increasing imaging speed
--------------------------------------------------------------------------------
OK, the Protocol.ini and the tcputils.ini files are located in the net folder for the various NIC's found in the Bootworks Configuration utility.
The tcpwindow size is defined by the number of servers you are connecting to from your client durring PXE boot. So if you have a Deployment Server and your images are then located on a separate file server you would be connecting to 2 servers in DOS Therefore you would need to enter a tcp windowsize=8700. You may wish to experiment with this a bit as it can be variable depending on the NIC you have on the client and also if you are using UNDI drivers or the correct DOS NIC driver. The tcpwindowsize must be specified in the [tcp] section of the protocol.ini
So the tcpwindowsize is as follows:
for 1 server tcpwindowsize= 11600
or tcpwindowsize= 10150
for 2 servers tcpwindowsize= 8700
for 3 server tcpwindowsize= 5800
for 4 server tcpwindowsize= 4350
for 5 server tcpwindowsize= 2900
for 6 server tcpwindowsize= 1450
The nbsessions setting is already in the protocol.ini and should simply be changed from the current number to the number of servers you are connecting to, which in the above example is 2 (a Deployment Server and a File Server). This setting also appears in the [tcp] section of the protocol.ini
numsockets is an entry which appears in the tcputils.ini file under the [Sockets] section and again should be changed to the number of servers, ie in this example 2.
You protocol.ini would now look a bit like this (note this is for the UNDI driver set and the rest of the configuration should NOT be changed to match this example, I have just included it for completeness):
Protocol.ini
------------"