dfsutil is useful on workstations for checking what's going on with the DFS shares that the client is subscribed to, e.g. by running dfsutil /pktinfo.
For Windows 10 pre-October 2018 dfsutil can be downloaded as part of RSAT Tools for Windows 10, but how do I get dfsutil for current versions of Windows 10?
The RSAT Tools download page gives a link to the list of RSAT tools available via Features on Demand in newer versions of Windows 10, however there are about 20 different RSAT features which you can download, and nothing in that page clearly says which one you need for dfsutil.
So, the full answer is:
Open Windows 10 settings
Search for 'Manage optional features'
Click on 'Add a feature'
Choose the package 'RSAT: File Services Tools' and click 'Install'
Depending on the precise version of Windows 10, you will either see the package installing immediately, or if not you will need to click back once to see installation progress
Wait to see the package finish installing
That's it, dfsutil is now available from Command Prompt and PowerShell; no reboot is needed.
You can add the optional feature with this PowerShell (admin) command:
Add-WindowsCapability -Online -Name "Rsat.FileServices.Tools~~~~0.0.1.0"
This will install dfsutil and also the DFS management console (dfsmgmt.msc)
Related
Platform Builder 5.0 is only supported on Windows 2000 and XP.
This question is to aid those looking for a way to run Platform Builder 5.0 on more recent operating systems.
A few reasons one might want to do that:
Corporate IT policy may not permit the use of Windows 2000/XP
With time, genuine copies of Windows 2000/XP may become increasingly hard to obtain
Depending on your overall setup and requirements, might eliminate the need for using a virtual machine for Platform Builder 5.0
You may simply wish to run a more modern and secure operating system
This answer explains how to install and run Platform Builder 5.0 on operating systems it is not officially supported on.
Windows Server 2008 and 2012
This procedure has been found to work on:
Windows Server 2008 (32-bit)
Windows Server 2012
Windows Server 2012 R2
It is recommended that you install Platform Builder before joining a Windows domain. I've had some issues getting the Platform Manager components registered while logged in as a domain user. See also the description further below.
Virus protection software might prevent the installation of .NET Framework 1.1, at least this has been a problem with Symantec Endpoint Protection. You may have to remove any security products before starting the installation (these may be re-installed later, but see the note below on the Full vs. Basic version of Symantec EP).
To install PB5, start by copying the contents of the installation CD (or mounted .iso) to a local folder, from here onwards referred to as the installation folder.
Use an .msi editor (like Orca) to remove the following entries from Microsoft Windows CE 5.0.msi in the installation folder:
OS version check (Table LaunchCondition, Action (MsiNTProductType=1 OR ...)
Emulator device driver (Table InstallExecuteSequence, Action CA_InstallVMMDriver.3D2F911E_A60A_4C07_8F7D_5306DC073E9A)
From the installation folder, run, in this order
ISScript8.msi (installs the InstallShield 8.0 script engine)
dotnetfx.exe (installs .NET Framework 1.1)
Microsoft Windows CE 5.0.msi (installs Platform Builder 5.0)
The installation may appear to hang at the Registering Platform Manager components step. It should proceed after a few minutes. If it is still stuck after, say, ten minutes, and your machine is joined to a Windows domain, then kill the installer in Task Manager, leave the domain and try installing again (you can rejoin after the installation is complete).
During the installation, you will receive a warning about compatibility issues. Select Don't show this warning again and click Run the program without getting help.
After the installation has finished, add a registry entry as follows.
If installing on a 32-bit system:
[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Shared Tools]
"SharedFilesDir"="C:\Program Files\Common Files\Microsoft Shared\"
Otherwise (installing on a 64-bit system):
[HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Microsoft\Shared Tools]
"SharedFilesDir"="C:\Program Files (x86)\Common Files\Microsoft Shared\"
Next, install Windows CE / Platform Builder updates as required (i.e. the "monthly updates" provided by Microsoft).
Optional: If any of your Windows CE targets require CJK support, you will need to update the cenlscmp tool to avoid an error during the makeimg phase. While this bug has long been fixed in Platform Builder 6.0 (PB6), the PB5 version has been left in the dust. So for CJK support you will need to copy cenlscmp from a PB6 installation, i.e. copy C:\WINCE600\PUBLIC\COMMON\OAK\BIN\I386\cenlscmp.exe to the corresponding folder in your new WINCE500 tree. Note that I've only tested the PB6 version; it is likely that newer versions would work too.
Optional: If you need support for building SDKs, you must make a copy of the Platform Builder help files, or a hard-coded assumption in the SDK builder will cause the build to fail. Copy the directory C:\Program Files (x86)\Windows CE Platform Builder\5.00\cepb\help to C:\Program Files\Windows CE Platform Builder\5.00\cepb\help.
Launch Platform Builder.
You will see a warning about compatibility issues. Select Don't show this warning again and click Run the program without getting help.
Optional: In the main window, click Tools | Customize. Click the Build OS menu once to open it. Drag the Build and Sysgen menu item out of the menu and drop it when the cursor displays a small 'X'. This will remove a dangerous command that, if clicked by accident, will require reinstalling Platform Builder. Hit Close to dismiss the Customize dialog box.
Platform Builder 5.0 is now ready to use, including the IDE itself, the build system, the help system, the debugger, and the run-time licensing tool.
Features that I haven't tested and which may or may not work include CETK and the emulator (the latter highly unlikely to work, as the emulator device driver had to be removed from the .msi).
If you use Symantec Endpoint Protection, be aware that the Full version may prevent pbxmlutils - an important Platform Builder tool - from running. This does not appear to be an issue with the Basic version.
One last hurdle is to configure the firewall to permit debugger traffic. To do this, open Windows Firewall with Advanced Security and
Under Inbound Rules, hit New Rule...
Select Program, Next
Enter the Path %ProgramFiles% (x86)\Windows CE Platform Builder\5.00\CORECON\BIN\cesvchost.exe, click Next
Ensure Allow the connection is selected, Next
Ensure Private and Domain are selected (but not Public, unless you really need this), Next
Enter a Name, e.g. "Platform Builder 5.0 debugger - cesvchost", Finish
Repeat the above with the path %ProgramFiles% (x86)\Common Files\Microsoft Shared\Windows CE Tools\Platman\bin\cemgr.exe.
Platform Builder will now be able to receive BOOTME frames, upload images, and connect to target with the kernel debugger.
Windows 7 and 8
The procedure documented above will not work for 64-bit Windows 7 or 8 (32-bit not tested).
Modifying the .msi as described makes the installation hang at the Registering Platform Manager components step. Removing the Platform Manager components from the installer causes a number of other issues, including failed registrations of the Help system and some common controls. More importantly, with Platform Manager missing it will not be possible to install any Windows CE/Platform Builder updates, making it virtually impossible to build any non-trivial CE project.
Windows 10
Not tested.
I know this isnt a dev question per se, but is there a timeline on a 5.2 build that can be installed on Win 10?
I think the issue i am seeing is just with the installer so an in place upgrade to Win 10 might work fine, but a clean install fails as it doesnt acknowledge IIS 10 or whatever version comes with Win 10.
Thanks!
Official answer - Windows 10 is not yet supported by the currently available Acumatica ERP installers, however the issue has already been fixed internally (AC-56069 - fixed in 4.20.2262, 5.10.0785, 5.20.1012 and newer). Following workaround can be used in the meantime:
Download the Orca tool to edit the MSI file: http://adriank.org/wp-content/uploads/2015/01/Orca.zip
Open the
MSI file using this tool (might be able to right click on MSI and
open with Orca)
Go to the LaunchCondition table
Drop/delete the IIS version condition (inside MSI, the LaunchCondition entry is IISVERSION >="#7"; system does a string comparison and "10" is
smaller than "7")
Save and close Orca
Run the setup
I can't give you an "official" answer but I can give you a work around.
If you download a utility called LessMSI you can extract the installation files. They will come out in a folder called "SourceDir". Simply take these and replace the files in your default installation folder or run them from another location.
Then you can proceed as normal.
The installer only checks if pre-reqs are installed and then copy's the files to the output location. If you have IIS already setup with dotnet support then the rest will be fine.
I do this frequently if I have to install a site with a specific version in order to upgrade or test a client's snapshot.
I have 4.1,4.2,5.1,5.2 running on my Windows 10 workstation as I type
i'm trying to install visual studio 2013 into my windows 7 32 bit system. I've encountered the below error during installation
"This update package could not be opened. Verify that the update package exists and that you can
access it, or contact the application vendor to verify that this is a valid Windows Installer
update package."
Help me out
it is windows so i am guessing: the installer package is corrupt or follow this link: http://kb.eset.de/esetkb/index?page=content&id=SOLN561
try to make some md5 sums of your files and google for them.
Normally this issue will occur if you are having permission issue or compatibility issue.
For permission issue:
Right click on the executable and run it with run as administrator option and check.
If above is not working then check for the compatibility issue by following the steps below:
To Run the installation program in compatibility mode:
1. Right-click the installation file's icon.
2. Click Properties > Compatibility .
3. Select the compatibility mode for Windows XP.
4. Click OK .
5. Run the installation program.
After it's installed, run the program in Windows XP compatibility mode by doing the same with the installed program.
If you have an older application for Windows XP or Vista that doesn't run in Windows 7, you may be able to get it working properly by running the program in compatibility mode.
1. To begin, find the application or shortcut that is causing the problem, then right click on it and select Properties.
2. Then, select Compatibility from the tabbed menu at the top of the properties page:
3. Now, check the "Run this program in compatibility mode for..." box and select the OS you wish to emulate. For most applications, it will be Windows XP SP2. Once you are done, click OK.
4. When you next launch the application it should run under compatibility mode using the OS you selected. If it still fails to run correctly, try another OS selection in step 3 and try again.
I have a network with one server that is connected to the internet and some clients that are not.
I want to download and install Microsoft products on my server first and let the client computers download the installer later from the server.
The questions are
where does the WPI save the downloaded files?
is it possible to run WPI and force it to install the Microsoft products from the already downloaded files rather than downloading again from Microsoft's server.
Note: Assume there is no license issue, hopely :-)
It will be cached under %LocalAppData%\Microsoft\Web Platform Installer\installers if you are on Vista or above, or in the equivalent location on XP (there is no %LocalAppData% environment variable in XP).
If the products are downloaded, they will be installed again from the cached location, unless they were updated, which would change their hash and force Web PI to download them again. Moreover, you can copy the cache folder from one computer to another to the same location and Web PI will pick it up automatically and install products from cached installers.
Microsoft has released a tool called Web Platform Installer v4 Command Line which has a switch to prepare an offline installation. Quote from the page above:
Creates an offline cached copy of a specified set of products and
applications so you can install while offline
Example:
Ex: >WebPICMD.exe /Offline /Products:WebMatrix,SQLExpress /Path:c:\OfflineCache
The above will create an offline cache at c:\offlineCache that contains WebMatrix and all it's possible dependencies!
Update 2017
The link above is no longer valid (404). The page i found is
Web Platform Installer v5 Command Line (WebPICMD.exe) - RTW release
WebPI Command line
The Web Platform Installer v5 (WebPI) command line tool is now
available as part of the WebPI MSI! We've added a bunch of new
features and fix several issues, and now it's ready for it's full
release
On the page are two links
WebPI v5 x86.msi
WebPI v4 x64.msi
Microsoft has released a beta tool that will do this.
In windows 8 I found it here
%AppData%\Local\Microsoft\Web Platform Installer\installers
I am trying to create a Local IIS Website using ASP.NET.
When I click on New -----> Website and select the type as HTTP and from the dialog box if I select the option as LOCAL IIS WEBSITE I am getting a message as "IIS not installed on this computer"
When I checked in the Control Panel---->Add or remove programs ---->Add or remove windows components. The Option Internet Information Service is already checked marked.
But when I click on the Control Panel ---> Administrative Tools, I dont find the option as Internet Information Service.
I also have the root directory as C:\Inetpub\WWWRoot.
And when I give the following command in the VS command Prompt
aspnet_regiis.exe -i
It is giving the message as finished installing ASP.NET
Can any one help me in identifying whether IIS is installed in my system or not?
Please help me out!
go to Start->Run type inetmgr and press OK. If you get an IIS configuration screen. It is installed, otherwise it isn't.
You can also check ControlPanel->Add Remove Programs, Click Add Remove Windows Components and look for IIS in the list of installed components.
EDIT
To Reinstall IIS.
Control Panel -> Add Remove Programs -> Click Add Remove Windows Components
Uncheck IIS box
Click next and follow prompts to UnInstall IIS.
Insert your windows disc into the appropriate drive.
Control Panel -> Add Remove Programs -> Click Add Remove Windows Components
Check IIS box
Click next and follow prompts to Install IIS.
For Windows 7:
Control Panel > Programs > Programs and Features > Turn Windows Features On or Off > to turn on IIS click on Check box.
Check
Control Panel --> Administrative Tools --> Services --> IIS Admin
For reinstalling
How to remove and reinstall IIS 5.0, 5.1 and 6.0
In the menu, go to RUN > services.msc and hit enter to get the services window and check for the IIS ADMIN service. If it is not present, then reinstall IIS using your windows CD.
The quickest way to check is just to write "inetmgr" at run (By pressing Win + R) as a command, if a manager window is appeared then it's installed otherwise it isn't.
A lot of answers here describe how to manually check if IIS is installed.
One (of many) programmatic ways is to check if the file
C:\Windows\System32\inetsrv\w3wp.exe
exists, and maybe has a certain minimum version (such as 10.0.0.0 for IIS version 10).
IIS can be installed programmatically using DISM. You can also use DISM to check if IIS is installed, which may be "more correct", but is also more difficult to do than just checking for a file.
WARNING: If possible, do not hard-code the path C:\Windows\System32, especially not within a 32-bit process or installer, as it can be virtualized and mapped to C:\Windows\SysWOW64, which is NOT where IIS is installed (assuming a 64-bit OS). Depending on where you are implementing your check (installer prerequisites, PowerShell, native code, etc.), there are different ways to explicitly access the 64-bit/native system folder.
Background: w3wp.exe is the worker process image of IIS, so if IIS is installed with minimal features, then this file can be expected to exist.
As for version numbers, you can expect the following minimum versions of IIS to be installed in (source):
IIS 10 (>= 10.0.0.0) in Windows Server 2016 or higher and Windows 10 or higher
IIS 8.5 (>= 8.5.0.0) in Windows Server 2012 R2 or higher and Windows 8.1 or higher
http://localhost:80 (specify port configured)
OR
http://localhost (default port)
type above line in your browser you realize IIS installed or not
I simple gave below in all my browsers. I got image IIS7
http://localhost/
Refer this a step by step approach:
http://www.codeproject.com/Tips/365704/Install-IIS-on-Windows
For many users you have to enable the windows feature on then check IIS and then go with RUN followed by searching for inetmgr.
I needed to do this on a server over the CLI, and was able to do so in using powershell wit the following command:
Get-ItemProperty -Path registry::HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\InetStp\ | Select-Object