phenom

I found a way to deploy the Netmeeting configurations but its not with the resource kit. There are 2 way to do it, the first is by using GPO either locally or from the 2003 ADS, in the user section of GPO snapin you will find the Netmeeting policies in the windows components and you can set about everything in there. The other option is to use AUTO-IT, where you can script all the mouse clic and keystroke event into an executable and from there you can deploy it on all your machines. conclusion : the resource kit is not working at all on WIN XP pro

Yeah you are right, some of Netmeeting features like conferencing and few other stuff are now integrated in messenger, and that is why Microsoft is no longer supporting Netmeeting on XP but, we need Netmeeting for Remote Desktop Sharing. We are also using the XP remote desktop sharing but this XP tool doesnt let you gain control of an active XP session unless the user invites you. In netmeeting you can gain control of an active session to troubleshoot a problem so we want to deploy this repackaged Netmeeting installation. I am sure that it's possible to tweak the registry in XP so we can deploy this Netmeeting install there is a known work around that I obviously cant find. It's not an incompatibility issue that is for sure, it's more like Microsoft doesnt let you deploy Netmeeting on XP because they wont support it.

yes the netmeeting 3.01 that comes with the WinXP works beautifully but the only way I can set it up is by running conf.exe from the start/run and go through the wizard steps. I need to silently install Netmeeting that is why I need the resource kit wich is pretty simple to use.

We want to deploy a repackaged Netmeeting installation that we build from the Nm3Rk (Netmeeting resource Kit) but when we run the package on a windows XP OS, it returns the following message : "This version of NetMeeting doesn't run on this version of Windows" The funny thing is that when we run conf.exe Netmeeting 3.01 configuration wizard fires up and everything can be configured succesfully. I heard that there is a workaround for that issue with XP and the Netmeeting Resource Kit, but I cant find it. Does anyone knows how to correct this ? by the way the same package works fine on win2k pro

Check this out my friend Step 1 : make sure that your SYSPREP.inf file contains the following line under the [unattended] section : DriverSigningPolicy=Ignore Step 2 : this is the most important part, I thought that SYSPREP was smart enough to go through the entire directory structure of the OemPnPDriverPath but it doesnt seem to be the case. I had to be carefull of where and what I extract from the manufacturer driver package. Take a look at my drivers path structure. OemPnPDriversPath=BIN\AUDIO\gx240;BIN\AUDIO\gx260;BIN\AUDIO\gx270;BIN\MODEM\gx240;BIN\MODEM\gx260;BIN\MODEM\gx270; BIN\CHIPSET\gx240;BIN\CHIPSET\gx260;BIN\CHIPSET\gx270;BIN\NET\gx240;BIN\NET\gx260;BIN\NET\gx270;BIN\VIDEO\gx240;BIN\VIDEO\gx260;BIN\VIDEO\gx270 What I did here is instead of extracting the entire content of the package in C:\drivers\AUDIO;C:\drivers\NET;C:\drivers\VIDEO ... I only extracted the required WINXP files for each components of each model GX240, GX260, GX270. I had to seperate them because the driver packages are using same file names between models and we dont want to overwrite the files. So inside every model folders there are no subfolders, only INF, CAT, DLL, SYS, VXD etc... NO EXE and NO CAB files. I was surprised to see that this last test was successfull because all over the NET, people are saying that the last SYSPREP version for WINXP SP2 is suppose to browse the entire directory structure to find its driver, but beleive me, its not the case. Try this and come back to me. Good Luck

Hi Jawrakae I have the same exact issue, cant find a way to solve the problem, my sysprep.inf file is build exactly like yours, and I also made sure that the driver signing policy is set to Ignore in windows XP. The drivers never load during mini setup and I am building an image for the following systems : DELL Optiplex GX150, GX240, GX260 and GX270. The image dumping process goes beautifully but the drivers are never installed. As soon as I find out how to fix this issue I will reply again Phenom