Martin Zugec

Both of them (RestrictedSites and KillBits blocklist) R just .reg files... So it is system-wide protection, not only IE

BTW maybe someone find it interesting - I was preparing corporate strategy against spyware for two big companies... We prepared lab for testing purposes and installed software from "amateur" solutions like Spybot to professional like corporate PestPatrol - and what do U think? Using KillBits and RestrictedSites was quite enough strong protection, even against threats like CWS! It really surprised me I have to say. BTW from normal solutions the best one was from ex-Giant

Best is combination of IE-SpyAD and KillBits blocklist (http://www.spywareguide.com/blocklist.reg)

2Shotgun: Spyder is right... BITS is on clients (now it is v2) - it is acting like download manager, so clients wont lie down your server and your customers/users wont even notice that there is something downloaded on their computer. About shortcuts - URC is Unicenter Remote Control, USD is Unicenter Software Delivery and UAM is Unicenter Asset Management... These systems R quite performance-eaters, so if would SUS consume CPU or bandwidth, I would notice

We do of course... Look at the link jbm posted, it is No Error Dialog + Create Error Log File. Problem is, I never seen it working Tried to use 0x30 to have logs and error logs, but didnt work

2WildKat: Sorry, typo Try that link again

Sorry, I cant help... I am using network installation and every client contact server in order to configure office. I would recommend U to locate PackageCache with command I provided and then try to redirect Office to this source

Ah, how stupid I can be I saw this code at least 100 times and didnt notice THX for your help, it is true that other people see what we dont

This Office behavior is normal - Windows Installer use "cache" mode, it is not really installed, it is only published... To see cache for msi product, use command wmic product get Name, PackageCache

Ok, I will try to show difference between 0005 and 0006 including files and batch code: 0005 1.) NIC identificator is generated and saved to variable pci0: %ramd%\files\pciscan.exe %ramd%\files\ndis.map > nul 2.) device is loaded to memory: %ramd%\files\device %ramd%\files\ifshlp.sys > nul 3.) Protocol.ini and system.ini R copied from ini folder to net folder. In ini folder they R named by NIC identifier, e.g. E1000 protocol.ini files is pe1000.ini: type %ramd%\ini\p%pci0%.ini > %ramd%\net\protocol.ini type %ramd%\ini\s%pci0%.ini > %ramd%\net\system.ini 4.) Random computer name is generated: %ramd%\NET\COMPNAME.EXE > nul 5.) String **COMPUTERNAME** is changed to generated name in system.ini: %ramd%\NET\alter.exe %ramd%\net\system.ini "**COMPUTERNAME**" "%compname%" > nul 6.) Network connection is established... System.ini [network] filesharing=no printsharing=no autologon=yes computername=**COMPUTERNAME** lanroot=z:\NET username=instal reconnect=no dospophotkey=N lmlogon=1 logondomain=DOMAIN preferredredir=basic autostart=basic [network drivers] netcard=e1000.dos transport=tcpdrv.dos,nemm.dos devdir=z:\NET LoadRMDrivers=yes [Password Lists] *Shares=z:\NET\Share000.PWL Protocol.ini [network.setup] version=0x3110 netcard=ms$e1000,1,MS$e1000,1 transport=tcpip,TCPIP lana0=ms$e1000,1,tcpip [ms$e1000] DRIVERNAME=e1000$ [protman] drivername=PROTMAN$ PRIORITY=MS$NDISHLP [tcpip] NBSessions=6 DefaultGateway0=0 0 0 0 SubNetMask0= IPAddress0= DisableDHCP=0 DriverName=TCPIP$ BINDINGS=ms$e1000 LANABASE=0 0006 1.) NIC identificator is generated and saved to variable pci0: %ramd%\files\pciscan.exe %ramd%\files\ndis.map > nul 2.) device is loaded to memory: %ramd%\files\device %ramd%\files\ifshlp.sys > nul 3.) String **NIC** is changed to %pci0%: %ramd%\NET\alter.exe %ramd%\net\protocol.ini "**NIC**" "%PCI0%" > nul %ramd%\NET\alter.exe %ramd%\net\system.ini "**NIC**" "%PCI0%" > nul 4.) NIC driver is copied to NET folder: copy %ramd%\NIC\%pci0%.dos %ramd%\net\%pci0%.dos > nul 5.) Random computer name is generated: %ramd%\NET\COMPNAME.EXE > nul 6.) String **COMPUTERNAME** is changed to generated name in system.ini: %ramd%\NET\alter.exe %ramd%\net\system.ini "**COMPUTERNAME**" "%compname%" > nul 6.) Network connection is established... System.ini [network] filesharing=no printsharing=no autologon=yes computername=**COMPUTERNAME** lanroot=z:\NET username=instal reconnect=no dospophotkey=N lmlogon=1 logondomain=DOMAIN preferredredir=basic autostart=basic [network drivers] netcard=**NIC**.dos transport=tcpdrv.dos,nemm.dos devdir=z:\NET LoadRMDrivers=yes [Password Lists] *Shares=z:\NET\Share000.PWL [network.setup] version=0x3110 netcard=ms$**NIC**,1,MS$**NIC**,1 transport=tcpip,TCPIP lana0=ms$**NIC**,1,tcpip [ms$el90x] DRIVERNAME=**NIC**$ [protman] drivername=PROTMAN$ PRIORITY=MS$NDISHLP [tcpip] NBSessions=6 DefaultGateway0=0 0 0 0 SubNetMask0= IPAddress0= DisableDHCP=0 DriverName=TCPIP$ BINDINGS=ms$**NIC** LANABASE=0

2mattofak: Close On all my unattended installations I got three phrases - technical, applications and close. Technical - SW, that I use every time and that is working as "frame" for other applications... For example .Net FrameWork, Antivirus, remote control... This is installed as soon as possible. Second phrase is application, that depends on pc name, locality, department etc... The last phrase is close - disable wallpaper ("Installing system..."), create user account, migrate user settings from server, create accounts in server systems (USD, UAM, Sap) etc. This is also phrase, that is same for all computers. I know this is not what U wanted to know, but with this installation architecture U dont have dependencies problems as U have. Think about it

Thx for reply... Build 0005 is working - no problem at all. Only thing, that is not working is build 0006 - and the files protocol.ini and system.ini R the same, only one difference is how R they generated! So I know using %pci0% is all right (I use alter.exe protocol.ini "***NIC***" %pci0%, so it only replace string ***NIC*** with value of variable)

I am using network installation... Long time ago I decided choosing NIC in menu is not the professional way and I wanted to automate it. BUILD 0005 --------------------------------------------------------------------------------------------- I used PCIscan, take Vendor and Product number, find the product in .map file. Now I know the NIC (for example E1000 or b57). This value is stored in pci0 variable. Then I copy %pci0%.dos driver to Net directory. The copy system.ini and protocol.ini to Net directory (for example for E1000 there R 2 files: pe1000.ini and se1000.ini. I used "Copy s%pci0%.ini z:\net\system.ini) ---------------------------------------------------------------------------------------------- In build 0006 I changed only one thing - I am not copying protocol and system.ini files, instead I am changing values inside: from ***NIC*** to %pci0%. Protocol.ini and system.ini FILES R EXACTLY THE SAME as before!!! But when I run installation, I got error from netbind: Error: 33 Unable to bind I appreciate any suggestions

.Net needs restart... Place .net to technical part and WinXP Manager to application part (dont know, if U have divided installation like this)

If MCTs hints wouldnt work, I would try memory test (U can use tool directly from Microsoft - EDIT:http://oca.microsoft.com/en/windiag.asp). Also have a look to %windir%\minidump - can U see any files in this directory?

It is not necessery to have XP SP1 or SP2 clients... U can use SUS on w2k and xp OSs (and server OSs of course)... SUS is really great, maybe in your case I would wait for WUS (it will be here soon). Any other questions? BTW using SMS for hotfix delivery is not best idea... 2Shotgun: I must disagreee. Because of BITS SUS is extremly low cpu and bandwidth intensive. Oficial number (and I must agree with them) says PIII 500MHz can take care of about 50000 clients. My two SUS servers R running on normal server (USD, URC and UAM) and once I was involved in deploying 6 virtual SUS servers on normal server...

2jaclaz: THX, this is great! I programmed proprietary code for this, but this is more universal

My OEM is 50MB... Your problem will probably be because of dos limitation (OEM is transferred during text-mode setup)... Usuall way is to include only necessary files (in my case there is only 4MB, rest is for different device drivers) and to hold rest of files somewhere else on server and install them by RunOnceEx or RunOnce

2XtremeMac: getmac works only if U receive IP address - for example if your mac is refused by DHCP, it will show U MAC address 00-00-00-00-00-00 Also there is problem in inserting the mac address to variable, so U can use it later I can imagine it like this: U run mac.exe - it will find your mac address and insert it to variable %macaddress%. Thats all I need - search and replace can be perform by another way

winnt.exe /s:I:\I386 /u:C:\TEMP\unattend.txt /t:c this is mine... Works perfectly

2XtremeMac: I wanted to post request I think it would be good to make utility, that will be able to make following steps from DOS: 1.) find MAC address from computer 2.) open file, find this MAC and insert associated computer name to variable The point is useful for network installation, where U can associate PC name to machine from dos and modify unattend.txt I am preparing my boot medium for network unattended installations and this could be great for me

They were talking about w2k, not wxp...

Well, it is not common. I got Chassis Intrusion in my Dell Optiplexis, U activate it through BIOS settings (U can use DCCU to automate BIOS configuration). Than U catch SNMP traps through OpenManage system

Maxthon with SP2 is enough strong against spyware... Dont see any reason why to use another browser

Well, I think U should follow my advise - small partition created from dos and let it expand during install... If U use MsDosInitiated, U CANT perform installation