Downloads of v 0.5.0:


Last Update:

16 Sep 2013

Package Maintainer(s):

Software Author(s):

  • Rob Reynolds


windows 2003 win2003 mklink symlink vagrant

Windows 2003 Symlinks (MkLink)

This is not the latest version of Windows 2003 Symlinks (MkLink) available.

  • 1
  • 2
  • 3

0.5.0 | Updated: 16 Sep 2013



Downloads of v 0.5.0:



Software Author(s):

  • Rob Reynolds

  • 1
  • 2
  • 3
Windows 2003 Symlinks (MkLink) 0.5.0

This is not the latest version of Windows 2003 Symlinks (MkLink) available.

  • 1
  • 2
  • 3

Some Checks Have Failed or Are Not Yet Complete

Not All Tests Have Passed

Validation Testing Unknown

Verification Testing Unknown

Scan Testing Successful:

No detections found in any package files

Learn More

Deployment Method: Individual Install, Upgrade, & Uninstall

To install Windows 2003 Symlinks (MkLink), run the following command from the command line or from PowerShell:


To upgrade Windows 2003 Symlinks (MkLink), run the following command from the command line or from PowerShell:


To uninstall Windows 2003 Symlinks (MkLink), run the following command from the command line or from PowerShell:


Deployment Method:

📝 NOTE: This applies to both open source and commercial editions of Chocolatey.

1. Enter Your Internal Repository Url

(this should look similar to

2. Setup Your Environment

1. Ensure you are set for organizational deployment

Please see the organizational deployment guide

2. Get the package into your environment

  • Open Source or Commercial:
    • Proxy Repository - Create a proxy nuget repository on Nexus, Artifactory Pro, or a proxy Chocolatey repository on ProGet. Point your upstream to Packages cache on first access automatically. Make sure your choco clients are using your proxy repository as a source and NOT the default community repository. See source command for more information.
    • You can also just download the package and push it to a repository Download

3. Copy Your Script

choco upgrade win2003-mklink -y --source="'INTERNAL REPO URL'" --version="'0.5.0'" [other options]

See options you can pass to upgrade.

See best practices for scripting.

Add this to a PowerShell script or use a Batch script with tools and in places where you are calling directly to Chocolatey. If you are integrating, keep in mind enhanced exit codes.

If you do use a PowerShell script, use the following to ensure bad exit codes are shown as failures:

choco upgrade win2003-mklink -y --source="'INTERNAL REPO URL'" --version="'0.5.0'" 

Write-Verbose "Exit code was $exitCode"
$validExitCodes = @(0, 1605, 1614, 1641, 3010)
if ($validExitCodes -contains $exitCode) {
  Exit 0

Exit $exitCode

- name: Install win2003-mklink
    name: win2003-mklink
    version: '0.5.0'
    state: present

See docs at

chocolatey_package 'win2003-mklink' do
  action    :install
  source   'INTERNAL REPO URL'
  version  '0.5.0'

See docs at

cChocoPackageInstaller win2003-mklink
    Name     = "win2003-mklink"
    Version  = "0.5.0"
    Source   = "INTERNAL REPO URL"

Requires cChoco DSC Resource. See docs at

package { 'win2003-mklink':
  ensure   => '0.5.0',
  provider => 'chocolatey',
  source   => 'INTERNAL REPO URL',

Requires Puppet Chocolatey Provider module. See docs at

4. If applicable - Chocolatey configuration/installation

See infrastructure management matrix for Chocolatey configuration elements and examples.

This package was submitted prior to moderation and has not been approved. While it is likely safe for you, there is more risk involved.


Windows 2003 Symlinks (MkLink)

Currently this only supports symlinking folders from network shares to local paths, helping bring vagrant to Windows 2003.

This implements the behavior specified in my stack overflow answer (go vote it up)

You call it the same way you do for folders on other versions of windows, mklink /d sometargetfolder \some\shared\folder

And before you ask, this should also work on Windows XP.

You need Visual C++ Redistributable for VS2005 SP1 installed (which is not yet a chocolatey package).

Log in or click on link to see number of positives.

In cases where actual malware is found, the packages are subject to removal. Software sometimes has false positives. Moderators do not necessarily validate the safety of the underlying software, only that a package retrieves software from the official distribution point and/or validate embedded software against official distribution point (where distribution rights allow redistribution).

Chocolatey Pro provides runtime protection from possible malware.

Add to Builder Version Downloads Last Updated Status
Windows 2003 Symlinks (MkLink) 0.5.0 991 Monday, September 16, 2013 Unknown

This package has no dependencies.

Discussion for the Windows 2003 Symlinks (MkLink) Package

Ground Rules:

  • This discussion is only about Windows 2003 Symlinks (MkLink) and the Windows 2003 Symlinks (MkLink) package. If you have feedback for Chocolatey, please contact the Google Group.
  • This discussion will carry over multiple versions. If you have a comment about a particular version, please note that in your comments.
  • The maintainers of this Chocolatey Package will be notified about new comments that are posted to this Disqus thread, however, it is NOT a guarantee that you will get a response. If you do not hear back from the maintainers after posting a message below, please follow up by using the link on the left side of this page or follow this link to contact maintainers. If you still hear nothing back, please follow the package triage process.
  • Tell us what you love about the package or Windows 2003 Symlinks (MkLink), or tell us what needs improvement.
  • Share your experiences with the package, or extra configuration or gotchas that you've found.
  • If you use a url, the comment will be flagged for moderation until you've been whitelisted. Disqus moderated comments are approved on a weekly schedule if not sooner. It could take between 1-5 days for your comment to show up.
comments powered by Disqus