tguy

Not sure what you are trying to do but you can run WINNT32.EXE from a cd inside Windows NT/2000/XP/2003 in GUI mode. Simply type Start --> Run --> <Path to CD>\i386\WINNT32.EXE. This is how you normally would start an inplace upgrade. If you want to do a unattended install you would set up the source files on a network share and then connect to it, launch winnt32.exe from the share and your on your way. Syntax would be \\Server\Share\i386\winnt32.exe /u:unattend.txt /s:<path to source files> Hope this helps. tguy

You could also try the TXTSETUP.SIF method discussed in this forum, I have used this method successfully. Search the Device Drivers section of this Forum for mraid35x and TXTSETUP you should find the information you need. tguy

Try using the Windows Server 2003 Resource Kit or Administrator's Pak utility called DSMOVE.EXE. That should let you move the users from Test to Production as opposed to trusting those users in the Test domain in the Production domain. I don't believe their accounts will copy over, they will simply be able to logon as Test\User to the Production domain. That will not have an account Production\User. tguy

You could try enabling auditing on the security logs for logon/logoff events and then parsing the event logs or you could look at Quest Software's Reporter tool. It will generate all sorts of reports including security related ones. tguy

Yes you can logon to two separate domains by selecting the appropriate domain from the drop down list. Each domain you logon to will create a new profile on your PC so if there is information you want to share you will need to put it in a common shared folder. If you still have problems go to http://www.globesoft.com and check out MultiNetwork Manager. This will give you a GUI to help you manage multiple network connections. tguy

Hello, First off it sounds like you have already enable remote desktop connectivity on your desktop. If you are using a WIN2K or earlier desktop you will need to install the RDP client from Microsoft. Second as the other post said, you will need to make sure your desktop and server can establish a connection over TCP (not UDP) port 3389. Third, you will need to make sure your server is set to allow RDP connections. You do this the same way you do in WinXP by right-clicking My Computer, choosing Properties, clicking on the Remote tab and making sure "Allow users to connect remotely to this computer" is checked. That should do it for you. tguy

Yes, you can do that but you will need to install and configure the Exchange server software as part of the SBS setup. You will also need to have your ISP host DNS and MX records for your domain. tguy

You could try using Microsoft's delsrv.exe utility from the Resource Kit to delete the service and then reinstall the application package that installed the service to see if that clear's up your error. OR You could uninstall and reinstall the application itself to try and get the service to install correctly. It kind of sounds like the installation did not complete successfully to register the service on your system.

You will need to contact Microsoft and obtain the multi-lingual version of Windows 2000 Professional. It is a multi-cd set that you can use to install additional languages including Arabic I believe. Try MS Worldwide Fullfillment first. tguy

Try one convert method or another, in other words if you use FileSystem=ConvertNTFS then don't try and run it from the [GuiRunOnce] section or vice-versa. Chances are the conversion was already done by FileSystem=ConvertNTFS so the command line script would not run anyway.

See this link, this should help explain where cmdlines.txt works from. http://www.winnetmag.com/Windows/Article/A.../3773/3773.html

Try this: FileSystem=Convert NTFS tguy

Yes, you can set SNMP parameters during an unattended install. Consult the Microsoft Windows 2000 Guide to Unattended Setup.doc or the ref.chm help file. Both are found in the deploy.cab located in the Support Tools directory of your source CD depending on which OS you are installing. The parameters and settings are documented in these files. tguy

Create a folder called $OEM$ in your root directory, ie: C:\XPCD\$OEM$ Create a folder called $1 in the $OEM$ folder, ie: C:\XPCD\$OEM$\$1 Copy the i386 directory from your Windows XP CD to the $1 folder, you'll end up with: C:\XPCD\$OEM$\$1\i386 The source files will then automatically be copied to the hard disk during the installation. tguy

Review the ref.chm help file in the deploy.cab file located in the Support Tools directory on your source CD. It has the answers you are looking for. tguy

I would first check and see if Hebrew language support has been enabled in the browser, if that does not work, move on to the OS and see if you can enable it there. tguy

In the [Components] section of your WINNT.SIF or UNATTEND.TXT add the following: indexsrv_system=on tguy

Try adding this to the java install command line: reboot=reallysuppress tguy

Search this forum for "mraid35x" and txtsetup. This should explain the txtsetup.sif method for integrating new SCSI drivers without having to create a custom drivers.cab. tguy

Make sure your $OEM$ folder is at the root of the CD. All files and directories should be underneath the $OEM$ directory. When you go to execute the batch file, call it from the location that the $OEM$ placed on your hard drive. tguy

Is your OEMPreinstall=Yes or OEMPreinstall=No in the [unattended] section of your WINNT.SIF file? It should be OEMPreinstall=Yes to install [Components] and additional programs together. tguy

Make sure shutdown.exe is in a directory known to be in the Path variable, like C:\WINDOWS or C:\WINDOWS\SYSTEM32 tguy

You could use a vbScript called by your setup process to delete files from the Quick Launch folder. Here is the one I use: Set objFSO = CreateObject("Scripting.FileSystemObject") objFSO.DeleteFile "C:\Documents and Settings\Default User\Application Data\Microsoft\Internet Explorer\Quick Launch\Explorer.lnk Hope this helps. tguy

Yes it is. In the [Components] section of your unattend file, WINNT.SIF or UNATTEND.TXT enter the following: Indexsrv_system=On tguy

All you need to do is to copy the i386 directory from your source cd to the $OEM$\$1 directory. All the files will then be copied to the root of the system drive ie: C:\ so you end up with C:\i386 as the directory where your installation files reside. Hope this helps. tguy