{"id":358,"date":"2008-05-31T03:34:00","date_gmt":"2008-05-31T10:34:00","guid":{"rendered":"https:\/\/kb.terabyteunlimited.com\/kb-articles\/running-image-for-windows-remotely-using-microsoft-psexec\/"},"modified":"2026-02-25T16:51:12","modified_gmt":"2026-02-26T00:51:12","slug":"running-image-for-windows-remotely-using-microsoft-psexec","status":"publish","type":"lsvr_kba","link":"https:\/\/www.terabyteunlimited.com\/kb\/kb-articles\/running-image-for-windows-remotely-using-microsoft-psexec\/","title":{"rendered":"Running Image for Windows Remotely using Microsoft PsExec"},"content":{"rendered":"<p>One way to run Image for Windows (IFW) remotely is using the Microsoft utility <a href=\"http:\/\/technet.microsoft.com\/en-us\/sysinternals\/bb897553.aspx\" target=\"_blank\" rel=\"noopener\">PsExec<\/a>. \u00a0PsExec is free,\u00a0simple to use, and does not require you to install client software. \u00a0Once the remote system has been configured properly (as outlined below), running IFW with PsExec is done simply by running a command line on the local system.<br \/>\r\n<br \/>\r\nYou may run IFW on a remote system using PsExec without first installing IFW on it. \u00a0(This is possible because PsExec has the\u00a0ability to copy the IFW program to the remote system as part of its processing.) \u00a0If you wish to use PHYLock, however, it must always be installed on the remote system beforehand. Because of these considerations, the exact procedure for using PsExec with IFW depends on whether or not IFW and PHYLock are installed on the remote system.<br \/>\r\n<br \/>\r\nSome basic definitions before we begin: The \"local system\" is the one from which you will be initiating the PsExec command line. \u00a0The \"remote system\" is the one that IFW will run on to create the image whenever you invoke the PsExec command line from the local system.<\/p>\r\n<p><strong>Note:<\/strong> PsExec does not support running programs on remote systems running Windows XP Home. This version of Windows lacks some of the required\u00a0network functionality required by PsExec.<br \/>\r\n<br \/>\r\n<\/p>\r\n<hr \/>\r\n<p><strong><span style=\"color: #005858;\">Using PsExec with Image for Windows Installed on the Remote System<\/span><\/strong><\/p>\r\n<ol>\r\n\t<li>If you have not already done so, <a href=\"https:\/\/www.terabyteunlimited.com\/downloads-image-for-windows\/\" target=\"_blank\" rel=\"noopener\">download<\/a> the latest version of IFW and install it on the remote system. Then run IFW to enter the license name and key.<br \/>\r\n<br \/>\r\n<\/li>\r\n\t<li>Configure IFW as desired using <span style=\"font-family: Courier New;\">IFW.INI<\/span>\u00a0and\/or\u00a0<span style=\"font-family: Courier New;\">SERVICES.INS<\/span>. At the very least, the <span style=\"font-family: Courier New;\">IFW.INI<\/span> file must contain the license details.<br \/>\r\n<br \/>\r\n<ul type=\"disc\">\r\n\t<li>When IFW is run from the command line \u2014 as it will be when invoked by PsExec \u2014 only the global parameters in <span style=\"font-family: Courier New;\">IFW.INI<\/span>\u00a0are used (i.e. those settings specified in the <span style=\"font-family: Courier New;\">[Options]<\/span> section). \u00a0All other <span style=\"font-family: Courier New;\">IFW.INI<\/span>\u00a0settings will be ignored. \u00a0Please refer to the <a href=\"http:\/\/www.terabyteunlimited.com\/downloads\/ifw_en_manual.pdf\">Image for Windows User Manual<\/a> for more information.<br \/>\r\n<br \/>\r\n<\/li>\r\n\t<li>If you wish to use <span style=\"font-family: Courier New;\">IFW.INI<\/span> settings on the remote system, you can either create and configure the file manually (as described in the <a href=\"http:\/\/www.terabyteunlimited.com\/downloads\/ifw_en_manual.pdf\">Image for Windows User Manual<\/a>) or run and configure IFW and then use the copy of <span style=\"font-family: Courier New;\">IFW.INI<\/span> that it creates for you (this is generally the easiest, assuming the options you need are available in the GUI). \u00a0The file must reside in the IFW installation directory on the remote system (the default installation directory is \"<span style=\"font-family: Courier New;\">C:&#92;Program Files&#92;TeraByte Drive Image Backup and Restore Suite<\/span>\" for 32-bit versions of Windows and \"<span style=\"font-family: Courier New;\">C:&#92;Program Files (x86)&#92;TeraByte Drive Image Backup and Restore Suite<\/span>\" for 64-bit versions).<br \/>\r\n<br \/>\r\n<\/li>\r\n\t<li>If you want to manipulate Windows services on the remote system during the imaging operation, edit <span style=\"font-family: Courier New;\">SERVICES.INS<\/span> as needed. \u00a0Please refer to the <a href=\"http:\/\/www.terabyteunlimited.com\/downloads\/ifw_en_manual.pdf\">Image for Windows User Manual<\/a>\u00a0for more information on controlling services using <span style=\"font-family: Courier New;\">SERVICES.INS<\/span>. \u00a0If you wish to use <span style=\"font-family: Courier New;\">SERVICES.INS<\/span>, it must reside in the IFW installation directory.<br \/>\r\n<br \/>\r\n<\/li>\r\n<\/ul>\r\n<\/li>\r\n\t<li>Add the IFW installation directory to the system path of the remote system.\u00a0\u00a0<strong>Note:<\/strong> This step is <u>not<\/u> necessary if the complete path to <span style=\"font-family: Courier New;\">IMAGEW.EXE\/IMAGEW64.EXE<\/span> is specified in the PsExec command (see Example 4\u00a0below). Otherwise, this step\u00a0is necessary for PsExec to find the IFW program.<br \/>\r\n<br \/>\r\nThe exact steps for this vary slightly depending on your version of Windows and method used:<br \/>\r\n<br \/>\r\n<ol type=\"a\">\r\n\t<li>To use the Control Panel:\r\n\r\n<ol>\r\n\t<li>Open the Control Panel and run the <strong>System<\/strong> applet.<\/li>\r\n\t<li>Click the<strong> Advanced<\/strong> tab (under Windows Vista, Windows 7, and Windows 8.x\/10\/11, click <strong>Advanced system settings<\/strong> in the list on the left side).<\/li>\r\n\t<li>Click the <strong>Environment Variables<\/strong> button.<\/li>\r\n<\/ol>\r\n<br \/>\r\nTo use the Start Menu or Windows Search (Windows 7\/8.x\/10\/11):\r\n\r\n<ol>\r\n\t<li>Open the Start Menu or click in the Search box on the taskbar.<\/li>\r\n\t<li>Type \"environment\" into the box.<\/li>\r\n\t<li>Run the <strong>Edit the system environment variables<\/strong> item.<\/li>\r\n\t<li>The System Properties dialog will open with the <strong>Advanced<\/strong> tab active.<\/li>\r\n\t<li>Click the <strong>Environment Variables<\/strong> button.<br \/>\r\n<br \/>\r\n<\/li>\r\n<\/ol>\r\n<\/li>\r\n\t<li>Under <strong>System Variables<\/strong>, locate the environment variable named <strong>Path<\/strong> and double-click it (or click it once and then click the <strong>Edit...<\/strong> button).<br \/>\r\n<br \/>\r\n<\/li>\r\n\t<li>Depending on the version of Windows, the value for the Path variable will either be in an edit box containing all path directories separated by semicolons or listed in a table format with each directory on its own row. <br \/>\r\n<br \/>\r\n<em>Windows Vista, Windows 7\/8.x, and earlier versions of Windows 10:<\/em><br \/>\r\n<br \/>\r\nAt the very end of the string shown in the \"Variable value\" text box, add a semicolon followed by the IFW installation directory. \u00a0For example, if the path ends with this:<br \/>\r\n<br \/>\r\n<span style=\"color: #3333ff; font-family: Courier New;\">%SystemRoot%&#92;system32&#92;wbem<\/span><br \/>\r\n<br \/>\r\nChange it to this (assuming that \"<span style=\"font-family: Courier New;\">C:&#92;Program Files (x86)&#92;TeraByte Drive Image Backup and Restore Suite<\/span>\" is your installation directory):<br \/>\r\n<br \/>\r\n<span style=\"color: #3333ff;\"><span style=\"font-family: Courier New;\">%SystemRoot%&#92;system32&#92;wbem;C:&#92;Program Files (x86)&#92;TeraByte Drive Image Backup and Restore Suite<\/span><\/span><span style=\"color: #3333ff;\"><br \/>\r\n<\/span><br \/>\r\n<em>Later versions of Windows 10 &amp; Windows 11:<\/em><br \/>\r\n<br \/>\r\nClick the <strong>New<\/strong> button and enter the IFW installation directory.<br \/>\r\n<br \/>\r\n<\/li>\r\n\t<li>Click <strong>OK<\/strong> to save the path change, then click <strong>OK<\/strong> to close the <strong>Environment Variables<\/strong> window.<br \/>\r\n<br \/>\r\n<\/li>\r\n\t<li>Reboot the remote system to put this change into effect.<br \/>\r\n<br \/>\r\n<\/li>\r\n<\/ol>\r\n<\/li>\r\n\t<li>If you have not already done so, <a href=\"http:\/\/technet.microsoft.com\/en-us\/sysinternals\/bb897553.aspx\" target=\"_blank\" rel=\"noopener\">download<\/a> the latest version of PsTools to the local system, and extract <span style=\"font-family: Courier New;\">PSEXEC.EXE<\/span> from the PsTools archive to\u00a0<span style=\"font-family: Courier New;\">%WinDir%&#92;system32<\/span> on the local system.<br \/>\r\n<br \/>\r\n<\/li>\r\n\t<li>Proceed to the section below titled <a href=\"#idRunningIFW\"><strong>Running Image for Windows with PsExec<\/strong><\/a>.<\/li>\r\n<\/ol>\r\n<hr \/>\r\n<p><strong><span style=\"color: #005858;\">Using PsExec without Image for Windows Installed on the Remote System<\/span><br \/>\r\n<\/strong><\/p>\r\n<ol>\r\n\t<li>If you want to use PHYLock during the imaging of the remote system, you may download a <a href=\"http:\/\/www.terabyteunlimited.com\/downloads\/phylock_ifw2.zip\">standalone copy of PHYLock<\/a> and install it on the remote system.<br \/>\r\n<br \/>\r\n<ul type=\"disc\">\r\n\t<li>If you are unfamiliar with PHYLock, please refer to the knowledge base article titled <strong><a href=\"https:\/\/www.terabyteunlimited.com\/kb\/?p=352\" target=\"_blank\" rel=\"noopener\">Introduction to PHYLock<\/a><\/strong>.<br \/>\r\n<br \/>\r\n<\/li>\r\n\t<li><span style=\"color: #ff0000;\"><strong>Note:<\/strong><\/span> If you will have PHYLock \u2014 but not IFW \u2014 installed on the remote system, you must ensure that the version of IFW being run on the local system is compatible with the version of PHYLock installed on the remote system. \u00a0The best way to do this is to update PHYLock on the remote system whenever you update IFW on the local system, <em>if<\/em> the PHYLock driver has been updated. \u00a0You can tell if the\u00a0PHYLock driver has been updated when installing the IFW package by whether or not you are prompted to reboot at the completion of the installation. \u00a0If you <em>are not<\/em> prompted to reboot, PHYLock has not been updated. \u00a0If you <em>are<\/em> prompted to reboot, the PHYLock driver has been updated and you should <a href=\"http:\/\/www.terabyteunlimited.com\/downloads\/phylock_ifw2.zip\">update PHYLock<\/a> on the remote system as well.<br \/>\r\n<br \/>\r\n<\/li>\r\n<\/ul>\r\n<\/li>\r\n\t<li>If you are a registered user of IFW, use a text editor to create a file with the following content on the remote system:<br \/>\r\n<br \/>\r\n<span style=\"color: #3333ff;\">[LICENSE]\r\nProductKey=XXXX-XXXX-XXXX-XXXX-XXXX-XXXX<br \/>\r\nUser=User Name<\/span><br \/>\r\n<br \/>\r\nWhere <strong>User Name<\/strong> and <strong>XXXX-XXXX-XXXX-XXXX-XXXX-XXXX<\/strong> represent your own registered user name and key.<br \/>\r\n<br \/>\r\nSave the text file as <span style=\"font-family: Courier New;\">IFW.INI<\/span> in <span style=\"font-family: Courier New;\">%WinDir%&#92;system32<\/span> on the remote system (which is usually <span style=\"font-family: Courier New;\">C:&#92;WINDOWS&#92;System32<\/span>). <br \/>\r\n<br \/>\r\n<\/li>\r\n\t<li>If you have not already done so, <a href=\"https:\/\/www.terabyteunlimited.com\/downloads-image-for-windows\/\" target=\"_blank\" rel=\"noopener\">download<\/a> the latest version of IFW and install it on the local system. \u00a0(The main point here is to obtain the IFW program, <span style=\"font-family: Courier New;\">IMAGEW.EXE\/IMAGEW64.EXE<\/span>. \u00a0Once you have done so as described in a step to follow, you may uninstall IFW, if you wish.)<br \/>\r\n<br \/>\r\n<\/li>\r\n\t<li>Configure\u00a0IFW as desired using <span style=\"font-family: Courier New;\">IFW.INI<\/span>\u00a0and\/or\u00a0<span style=\"font-family: Courier New;\">SERVICES.INS<\/span>. At the very least, the <span style=\"font-family: Courier New;\">IFW.INI<\/span> file must contain the license details.<br \/>\r\n<br \/>\r\n<ul type=\"disc\">\r\n\t<li>When IFW is run from the command line \u2014 as it will be when invoked by PsExec \u2014 only the global parameters in <span style=\"font-family: Courier New;\">IFW.INI<\/span>\u00a0are used (i.e. those settings specified in the <span style=\"font-family: Courier New;\">[Options]<\/span> section). \u00a0All other <span style=\"font-family: Courier New;\">IFW.INI<\/span>\u00a0settings will be ignored. \u00a0Please refer to the <a href=\"http:\/\/www.terabyteunlimited.com\/downloads\/ifw_en_manual.pdf\">Image for Windows User Manual<\/a> for more information.<br \/>\r\n<br \/>\r\n<\/li>\r\n\t<li>If you wish to use <span style=\"font-family: Courier New;\">IFW.INI<\/span> settings on the remote system, you can either configure the file manually (as described in the <a href=\"http:\/\/www.terabyteunlimited.com\/downloads\/ifw_en_manual.pdf\">Image for Windows User Manual<\/a>) or run and configure IFW and then use the copy of <span style=\"font-family: Courier New;\">IFW.INI<\/span> that it creates for you (this is generally the easiest, assuming the options you need are available in the GUI). \u00a0If you wish to use <span style=\"font-family: Courier New;\">IFW.INI<\/span> without having IFW installed, it must reside in\u00a0<span style=\"font-family: Courier New;\">%WinDir%&#92;System32<\/span>\u00a0on the remote system (again, this is usually <span style=\"font-family: Courier New;\">C:&#92;WINDOWS&#92;System32<\/span>). Note: The IFW license information will also need to be in the <span style=\"font-family: Courier New;\">IFW.INI<\/span> file (as shown in Step 2).<br \/>\r\n<br \/>\r\n<\/li>\r\n\t<li>If you want to manipulate Windows services on the remote system during the imaging operation, create and\/or edit <span style=\"font-family: Courier New;\">SERVICES.INS<\/span> as needed. \u00a0Please refer to the <a href=\"http:\/\/www.terabyteunlimited.com\/downloads\/ifw_en_manual.pdf\">Image for Windows User Manual<\/a>\u00a0for more information on controlling services using <span style=\"font-family: Courier New;\">SERVICES.INS<\/span>. \u00a0If you wish to use <span style=\"font-family: Courier New;\">SERVICES.INS<\/span>,\u00a0it must be placed in\u00a0<span style=\"font-family: Courier New;\">%WinDir%&#92;System32<\/span> on the remote system.<br \/>\r\n<br \/>\r\n<\/li>\r\n<\/ul>\r\n<\/li>\r\n\t<li>If you wish to uninstall IFW from the local system, first locate <span style=\"font-family: Courier New;\">IMAGEW.EXE\/IMAGEW64.EXE<\/span>\u00a0in the IFW installation directory, and copy it to <span style=\"font-family: Courier New;\">%WinDir%&#92;System32<\/span> on the local system. \u00a0(The default installation directory is \"<span style=\"font-family: Courier New;\">C:&#92;Program Files&#92;TeraByte Drive Image Backup and Restore Suite<\/span>\" for 32-bit versions of Windows and \"<span style=\"font-family: Courier New;\">C:&#92;Program Files (x86)&#92;TeraByte Drive Image Backup and Restore Suite<\/span>\" for 64-bit versions.)<br \/>\r\n<br \/>\r\n<\/li>\r\n\t<li>If you have not already done so, <a href=\"http:\/\/technet.microsoft.com\/en-us\/sysinternals\/bb897553.aspx\" target=\"_blank\" rel=\"noopener\">download<\/a> the latest version of PsTools to the local system, and extract <span style=\"font-family: Courier New;\">PSEXEC.EXE<\/span> from the PsTools archive to\u00a0<span style=\"font-family: Courier New;\">%WinDir%&#92;System32<\/span> on the local system.<br \/>\r\n<br \/>\r\n<\/li>\r\n\t<li>Proceed to the section below titled <strong>Running Image for Windows with PsExec<\/strong>.<\/li>\r\n<\/ol>\r\n<hr \/>\r\n<p id=\"idRunningIFW\"><strong><span style=\"color: #005858;\">Running Image for Windows with PsExec<\/span><\/strong><\/p>\r\n<p>Create a shortcut or batch file on the local system for running PsExec. \u00a0This is where you will specify the command line parameters for both PsExec and IFW.<\/p>\r\n<ul>\r\n\t<li>More information on PsExec command line parameters can be found on the <a href=\"http:\/\/technet.microsoft.com\/en-us\/sysinternals\/bb897553.aspx\" target=\"_blank\" rel=\"noopener\">PsExec home page<\/a> or by running <span style=\"font-family: Courier New;\">PSEXEC.EXE<\/span> without parameters.<br \/>\r\n<br \/>\r\n<\/li>\r\n\t<li>More information on IFW command line parameters can be found in the <a href=\"http:\/\/www.terabyteunlimited.com\/downloads\/ifw_en_manual.pdf\">Image for Windows User Manual<\/a>.<\/li>\r\n<\/ul>\r\n<p>Here are some example command lines:<\/p>\r\n<p><strong><span style=\"color: #ff0000;\">Example 1<br \/>\r\n<\/span><\/strong><br \/>\r\n<span style=\"color: #3333ff; font-family: Courier New;\">psexec.exe &#92;&#92;RemoteComputerName -u Administrator -s -c -v <\/span><span style=\"color: #3333ff;\"><span style=\"font-family: Courier New;\">\"C:&#92;Program Files (x86)&#92;TeraByte Drive Image Backup and Restore Suite&#92;imagew64.exe\"<\/span><\/span><span style=\"color: #3333ff; font-family: Courier New;\"> \/b \/uy\u00a0\/d:w0@0x1 \/f:\"D:&#92;Backups&#92;WinBackup\" \/vb<\/span><br \/>\r\n<br \/>\r\nThe command above, which assumes that IFW is installed to \"<span style=\"font-family: Courier New;\">C:&#92;Program Files (x86)&#92;TeraByte Drive Image Backup and Restore Suite<\/span>\" on the local system, will:\u00a0<\/p>\r\n<ul>\r\n\t<li>Copy \"<span style=\"font-family: Courier New;\">C:&#92;Program Files (x86)&#92;TeraByte Drive Image Backup and Restore Suite&#92;imagew64.exe<\/span>\"\u00a0to the computer named \"<span style=\"font-family: Courier New;\">RemoteComputerName<\/span>\". \u00a0This is the approach you would generally use if IFW were installed on the local system, but not on the remote system.<br \/>\r\n<br \/>\r\n<\/li>\r\n\t<li>Run IFW, using the specified IFW parameters, as <span style=\"font-family: Courier New;\">Administrator<\/span> on the remote computer. \u00a0Since the <span style=\"font-family: Courier New;\">-p<\/span> parameter was not supplied, PsExec will prompt for the <span style=\"font-family: Courier New;\">Administrator<\/span> password.<\/li>\r\n<\/ul>\r\n<p><strong><span style=\"color: #ff0000;\">Example 2<br \/>\r\n<\/span><\/strong><br \/>\r\n<span style=\"color: #3333ff; font-family: Courier New;\">psexec.exe &#92;&#92;RemoteComputerName -u Administrator -p AdminPassword\u00a0-s -c -v imagew64.exe \/b \/uy\u00a0\/d:w0@0x1 \/f:\"D:&#92;Backups&#92;WinBackup\" \/vb<\/span><br \/>\r\n<br \/>\r\nThe command above will:<\/p>\r\n<ul>\r\n\t<li>Copy\u00a0<span style=\"font-family: Courier New;\">imagew64.exe<\/span>\u00a0to the computer named \"<span style=\"font-family: Courier New;\">RemoteComputerName<\/span>\".<br \/>\r\n<br \/>\r\n<\/li>\r\n\t<li>Run IFW, using the specified IFW parameters, as <span style=\"font-family: Courier New;\">Administrator<\/span> on the remote computer. \u00a0The password <span style=\"font-family: Courier New;\">AdminPassword<\/span> will be supplied.<\/li>\r\n<\/ul>\r\n<p><strong><span style=\"color: #ff0000;\">Example 3<br \/>\r\n<\/span><\/strong><br \/>\r\n<span style=\"color: #3333ff; font-family: Courier New;\">psexec.exe &#92;&#92;RemoteComputerName -u Administrator -p AdminPassword\u00a0-s imagew64.exe \/b \/uy\u00a0\/d:w0@0x1 \/f:\"D:&#92;Backups&#92;WinBackup\" \/vb<\/span><br \/>\r\n<br \/>\r\nThe command above will:<\/p>\r\n<ul>\r\n\t<li>Assume that <span style=\"font-family: Courier New;\">IMAGEW64.EXE<\/span> can be found in the system path of the the computer named \"<span style=\"font-family: Courier New;\">RemoteComputerName<\/span>\" (note that the <span style=\"font-family: Courier New;\">-c<\/span> parameter is not present). \u00a0This is the approach you would generally use if IFW were installed on the remote system.<br \/>\r\n<br \/>\r\n<\/li>\r\n\t<li>Run IFW, using the specified IFW parameters, as <span style=\"font-family: Courier New;\">Administrator<\/span> on the remote computer. \u00a0The password <span style=\"font-family: Courier New;\">AdminPassword<\/span> will be supplied.<\/li>\r\n<\/ul>\r\n<p><strong><span style=\"color: #ff0000;\">Example 4<br \/>\r\n<\/span><\/strong><br \/>\r\n<span style=\"color: #3333ff; font-family: Courier New;\">psexec.exe &#92;&#92;RemoteComputerName -u Administrator -p AdminPassword\u00a0-s \"C:&#92;Program Files (x86)&#92;TeraByte Drive Image Backup and Restore Suite&#92;imagew64.exe\" \/b \/uy\u00a0\/d:w0@0x1 \/f:\"D:&#92;Backups&#92;WinBackup\" \/vb<\/span><br \/>\r\n<br \/>\r\nThe command above will:<\/p>\r\n<ul>\r\n\t<li>Assume that <span style=\"font-family: Courier New;\">IMAGEW64.EXE<\/span> is installed on the remote system and can be found in the\u00a0\"<span style=\"font-family: Courier New;\">C:&#92;Program Files (x86)&#92;TeraByte Drive Image Backup and Restore Suite<\/span>\" directory of the the computer named \"<span style=\"font-family: Courier New;\">RemoteComputerName<\/span>\". \u00a0This is the approach you would generally use if IFW were installed on the remote system and you did not want to add the IFW path to the Path variable of the remote system.<br \/>\r\n<br \/>\r\n<\/li>\r\n\t<li>Run IFW, using the specified IFW parameters, as <span style=\"font-family: Courier New;\">Administrator<\/span> on the remote computer. \u00a0The password <span style=\"font-family: Courier New;\">AdminPassword<\/span> will be supplied.<\/li>\r\n<\/ul>\r\n<p><strong><span style=\"color: #ff0000;\">Example 5<br \/>\r\n<\/span><\/strong><br \/>\r\n<span style=\"color: #3333ff; font-family: Courier New;\">psexec.exe &#92;&#92;RemoteComputerName -u DomainName&#92;Administrator -p AdminPassword\u00a0-s imagew64.exe \/b \/uy\u00a0\/d:w0@0x1 \/f:\"D:&#92;Backups&#92;WinBackup\" \/vb<\/span><br \/>\r\n<br \/>\r\n<\/p>\r\n<p>The command above is identical to Example 3, except that by adding \"<span style=\"color: #3333ff; font-family: Courier New;\">DomainName&#92;<\/span>\", it uses the <em>domain <\/em>administrator account, rather than the <em>local<\/em> administrator account.\u00a0 Using the Domain Administrator account may be useful in some environments.<\/p>\r\n<hr \/>\r\n<p><strong><span style=\"color: #ff5500;\">Technical Notes:<\/span><\/strong><br \/>\r\n<br \/>\r\n<\/p>\r\n<p><strong><span style=\"color: #005858;\">Running the\u00a0Remote Process in the System Account<\/span><\/strong><\/p>\r\n<p>If the remote system is running Windows Vista or Windows 7\/8.x\/10\/11, you must specify the <span style=\"color: #0003ff; font-family: courier new,courier,monospace;\">-s<\/span> option (as shown in the examples). If this option is omitted,\u00a0IFW won't be run. This option isn't required for the program to run under Windows XP Professional.<\/p>\r\n<p>&nbsp;<\/p>\r\n<p><strong><span style=\"color: #005858;\">Have IFW Run Interactively<\/span><\/strong><\/p>\r\n<p>If you want to have IFW run interactively on the remote system (have the GUI shown), you can specify the <span style=\"color: #0003ff; font-family: Courier New;\">-i<\/span> option. For example:<br \/>\r\n<br \/>\r\n<span style=\"color: #3333ff; font-family: Courier New;\">psexec.exe &#92;&#92;RemoteComputerName -u Administrator -p AdminPassword\u00a0-s -i \"C:&#92;Program Files (x86)&#92;TeraByte Drive Image Backup and Restore Suite&#92;imagew64.exe\" \/b \/uy\u00a0\/d:w0@0x1 \/f:\"D:&#92;Backups&#92;WinBackup\" \/vb<\/span><\/p>\r\n<p>&nbsp;<\/p>\r\n<p><strong><span style=\"color: #005858;\">\"Access is denied\" When Remote System is Running Windows Vista or Windows 7\/8.x\/10\/11<\/span><\/strong><\/p>\r\n<p>UAC remote restrictions may need to be disabled. Please see the following Microsoft KB article for more information: <a href=\"http:\/\/support.microsoft.com\/kb\/951016\" target=\"_blank\" rel=\"noopener\">Description of User Account Control and remote restrictions in Windows Vista<\/a><\/p>\r\n<p>&nbsp;<\/p>\r\n<p><strong><span style=\"color: #005858;\">Login Information May Be Required to Access Network Shares<\/span><\/strong><\/p>\r\n<p>If IFW needs to access any network shares (especially those on later versions of Windows, such as Vista or Windows 7\/8.x\/10\/11), you may be required to provide the login information. Not providing this information may cause IFW to abort.<\/p>\r\n<p>Here is an example accessing the <strong>&#92;&#92;myserver&#92;backups<\/strong> share using <strong>JohnDoe<\/strong> for the user name and <strong>pswd1234<\/strong> for the password:<br \/>\r\n<br \/>\r\n<span style=\"color: #3333ff; font-family: Courier New;\">psexec.exe &#92;&#92;RemoteComputerName -u Administrator -p AdminPassword -s \"C:&#92;Program Files (x86)&#92;TeraByte Drive Image Backup and Restore Suite&#92;imagew64.exe\" <br \/>\r\n\/login:\"&#92;&#92;myserver&#92;backups*myserver&#92;JohnDoe*pswd1234\"<br \/>\r\n\/b \/uy \/d:w0@0x1 \/f:\"&#92;&#92;myserver&#92;backups&#92;WinBackup\" \/vb<\/span><\/p>\r\n<p>More information on using <span style=\"color: #3333ff;\">\/login:<\/span> can be found in the <a href=\"http:\/\/www.terabyteunlimited.com\/downloads\/ifw_en_manual.pdf\" target=\"_blank\" rel=\"noopener\">Image for Windows manual<\/a>.<\/p>","protected":false},"excerpt":{"rendered":"<p>One way to run Image for Windows (IFW) remotely is using the Microsoft utility PsExec. \u00a0PsExec is free,\u00a0simple to use, and does not require you to install client software. \u00a0Once the remote system has been configured properly (as outlined below), running IFW with PsExec is done simply by running a command line on the local [&hellip;]<\/p>\n","protected":false},"author":5,"featured_media":0,"comment_status":"closed","ping_status":"closed","template":"","meta":{"footnotes":""},"lsvr_kba_cat":[1796],"lsvr_kba_tag":[2121],"class_list":["post-358","lsvr_kba","type-lsvr_kba","status-publish","hentry","lsvr_kba_cat-general-information-image-for-windows","lsvr_kba_tag-image-for-windows"],"_links":{"self":[{"href":"https:\/\/www.terabyteunlimited.com\/kb\/wp-json\/wp\/v2\/lsvr_kba\/358","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.terabyteunlimited.com\/kb\/wp-json\/wp\/v2\/lsvr_kba"}],"about":[{"href":"https:\/\/www.terabyteunlimited.com\/kb\/wp-json\/wp\/v2\/types\/lsvr_kba"}],"author":[{"embeddable":true,"href":"https:\/\/www.terabyteunlimited.com\/kb\/wp-json\/wp\/v2\/users\/5"}],"replies":[{"embeddable":true,"href":"https:\/\/www.terabyteunlimited.com\/kb\/wp-json\/wp\/v2\/comments?post=358"}],"version-history":[{"count":5,"href":"https:\/\/www.terabyteunlimited.com\/kb\/wp-json\/wp\/v2\/lsvr_kba\/358\/revisions"}],"predecessor-version":[{"id":7304,"href":"https:\/\/www.terabyteunlimited.com\/kb\/wp-json\/wp\/v2\/lsvr_kba\/358\/revisions\/7304"}],"wp:attachment":[{"href":"https:\/\/www.terabyteunlimited.com\/kb\/wp-json\/wp\/v2\/media?parent=358"}],"wp:term":[{"taxonomy":"lsvr_kba_cat","embeddable":true,"href":"https:\/\/www.terabyteunlimited.com\/kb\/wp-json\/wp\/v2\/lsvr_kba_cat?post=358"},{"taxonomy":"lsvr_kba_tag","embeddable":true,"href":"https:\/\/www.terabyteunlimited.com\/kb\/wp-json\/wp\/v2\/lsvr_kba_tag?post=358"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}