Наконец, я надеюсь узнать причину и протестировать некоторые сценарии.
Во-первых, позвольте мне заявить, что это ошибка Windows NFS.
Я не знаю, как сообщить об этом в Microsoft как о смертном. Я буду сообщать об этом здесь и в моем блоге.
Есть условия, которые должны быть выполнены для распространения этой ошибки:
1) компьютер должен быть в домене
2) Вы должны использовать этот компьютер как во внутренней сети, так и в полноценном VPN, и вы должны оба в одном профиле.
3) У вас должна быть установлена реализация Microsoft NFS (псевдоним Client для NFS)
4) Служба должна запускаться автоматически при запуске компьютера. Если служба находится в режиме manual запуска и запускается после завершения последовательности загрузки, ошибка не проявится.
5) У вас должен быть какой-то общий ресурс NFS. Проблема здесь в том, что доля NFS имеет приоритет над обычной долей net use . Если вы отключите общий ресурс NFS, а затем отобразите его, используя net use ... /persistent:yes , этот ресурс будет перезаписан после перезагрузки. После перезагрузки он будет идентифицирован как общий ресурс NFS , который выдает ошибку.
Как с этим бороться?
Вкратце: установите для службы NFS Client for Windows ручной режим из автоматического режима. Используйте планировщик задач или gpedit в сочетании с моими сценариями powershell для монтирования и размонтирования общих ресурсов NFS.
НЕ останавливайте службу NFS Client for Windows при подключении некоторых общих ресурсов!
Более длинный ответ:
При использовании моих сценариев, пожалуйста, прочитайте ниже информацию:
Примечания && лучшие практики (важно прочитать!):
A) NFS mount, at least the Microsoft's implementation, is NOT persistent over boots. To overcome
this you have these options:
I) Schedule this script in Task scheduler under "ordinary" user e.g. DOMAINuser and have the
check-box "Run with highest privileges" (in order to start the NFS Client service if stopped)
II) Run it in the "Local Group Policy Editor" (gpedit.msc) under "Windows SettingsScripts"
(Startup -> mount and Shutdown -> unmount) in the sections "Computer Configuration" (for all
users) or under "User configuration" (for one specific user)
B) Do !!!NOT!!! mount NFS drive on system-wide account as "nt authoritysystem". At the first
glance this seems to be a good idea. Don't be fooled, it is not! When you mount NFS share
under "SYSTEM" account it will appear as fixed drive for all other users! On "SYSTEM" account
it still will show as network share. If you stop the NFS Client for Windows service, NOT
recommended when any NFS share active, and then start it again, then even under "SYSTEM"
account it will appear as "fixed" drive. It will leave user no option other than restart for
unmount.
C) It is NOT a good idea to stop Client for NFS Service when you have NFS mounted. It can lead
to unexpected states like the NFS share actually becoming a hard-drive for windows till reboot.
D) If the Client for NFS Service is started already then it is better not to stop it manually as
it can, under certain circumstances, refuse to start. It is better to have a log-off script
take care of the unmount && stopping the service
Ошибки или замечания по конфигурации сервера:
A) You are getting a powershell error:
"Attempting to perform the InitializeDefaultDrives operation on the 'FileSystem' provider
failed."
This error can be caused the NFS Client for Windows when service is starting with start of the
Windows. It takes precedence over "ordinary" `net use` and it causes powershell to check
"FileSystem".
Ad A) Решение: используйте этот скрипт для монтирования NFS Share — установите его при помощи политик gpedit при запуске или
Вы можете запустить через планировщик задач (он пытается запустить службу «Клиент для NFS») — у сценария должны быть права на это. Не забудьте установить службу «Клиент для NFS» («NfsClnt»)
к ручному запуску, чтобы он не запускался при запуске Windows.
B) If you are getting this error message (at your NFS server):
"(rpc.mountd[7243]: refused mount request from 192.168.XX.XX for <mount>: illegal port 24784"
you are most probably trying to connect on port over 1024. To connect to NFS share you need
to have 'insecure' option at your /etc/exports (if missing fix it and run `exportfs -r`)
СОВЕТ: Для запуска сценария монтирования требуется UAC, если служба еще не запущена. Вы можете:
1) run it manually - you will see UAC window 2) create a new Task in Task Scheduler and check the check box "Run it with highest privileges" 3) create a startup powershell script in the local policies
Миграция с сетевого диска NFS OR на общий ресурс (например, с использованием автономных функций Windows) в облако
Удаление сетевого диска (в моем случае диск U: 
Эта проблема может возникнуть, если у вас включена автономная работа с файлами, и файлы резервируются на сетевой диск. Если ваша компания изменит это в пользу перехода на какой-либо облачный сервис, это может привести к тупиковой ситуации в вашем профиле, когда некоторым приложениям все еще нужен предыдущий сетевой диск, но вам все равно нужно переключиться на нового облачного провайдера.
Если вы используете NFS Client for windows от Microsoft, вот как вы избавляетесь от предыдущего сетевого диска:
Как избавился от диска U: (пока нет сообщения) со следующими шагами:
1) Выберите -> Start MenuProgramsAdministrative ToolsServices for Network File System (NFS)
2) Остановите client for NFS щелкнув правой кнопкой мыши на элементе и выбрав « stop service
3) Простое ручное удаление работает !!!!
net use u: /delete
--> U: was deleted successfully.
Чтобы Windows забыла предыдущий диск и правильно установила в Volatile Environment новую конфигурацию, вам необходимо перезагрузить компьютер.
Сообщение об ошибке не отображается при остановленном Client for NFS . Достаточно иметь это в государственном manual и запустить его через скрипт
Finally, I hope to know the reason and tested some scenarios.
First, let me state that this is a Windows NFS BUG.
I don’t know how to report it to Microsoft as mere mortal. I’ll be reporting it here and on my blog.
There are conditions to be met for this error to propagate:
1) The computer must be in domain
2) You have to use this computer both on internal network and full-fledged VPN and you have to both on the same profile
3) You have to have the Microsoft’s NFS implementation installed (alias Client for NFS)
4) You have to have the service started automatically at the start of the computer. If the service is on manual start and is started after the boot sequence is complete the bug will not manifest itself.
5) You have to have some kind of NFS share. The issue here is that the NFS share takes precedence over ordinary net use share. If you disconnect a NFS share and then map it using net use ... /persistent:yes, then this share will get overwritten after a reboot. It will be identified, after reboot, as NFS share again, and producing the error.
How to deal with it?
In short:
Set the NFS Client for Windows service to manual from automatic mode. Use Task Scheduler or gpedit in conjunction with my powershell scripts for mounting and unmounting NFS shares.
DO NOT stop NFS Client for Windows service when some shares are mounted!
Longer answer:
When using my scripts please read the bellow information:
Notes && best practices (important to read!):
A) NFS mount, at least the Microsoft's implementation, is NOT persistent over boots. To overcome
this you have these options:
I) Schedule this script in Task scheduler under "ordinary" user e.g. DOMAINuser and have the
check-box "Run with highest privileges" (in order to start the NFS Client service if stopped)
II) Run it in the "Local Group Policy Editor" (gpedit.msc) under "Windows SettingsScripts"
(Startup -> mount and Shutdown -> unmount) in the sections "Computer Configuration" (for all
users) or under "User configuration" (for one specific user)
B) Do !!!NOT!!! mount NFS drive on system-wide account as "nt authoritysystem". At the first
glance this seems to be a good idea. Don't be fooled, it is not! When you mount NFS share
under "SYSTEM" account it will appear as fixed drive for all other users! On "SYSTEM" account
it still will show as network share. If you stop the NFS Client for Windows service, NOT
recommended when any NFS share active, and then start it again, then even under "SYSTEM"
account it will appear as "fixed" drive. It will leave user no option other than restart for
unmount.
C) It is NOT a good idea to stop Client for NFS Service when you have NFS mounted. It can lead
to unexpected states like the NFS share actually becoming a hard-drive for windows till reboot.
D) If the Client for NFS Service is started already then it is better not to stop it manually as
it can, under certain circumstances, refuse to start. It is better to have a log-off script
take care of the unmount && stopping the service
Errors or server configuration notes:
A) You are getting a powershell error:
"Attempting to perform the InitializeDefaultDrives operation on the 'FileSystem' provider
failed."
This error can be caused the NFS Client for Windows when service is starting with start of the
Windows. It takes precedence over "ordinary" `net use` and it causes powershell to check
"FileSystem".
Ad A) Solution: Use this script for mounting NFS Share — set it using
gpedit policies on start or
you can run via Task scheduler (It tries to start the Client for NFS service) — the script has
to have rights to do so Don’t forget to set the service «Client for NFS»(«NfsClnt»)
to manual start so it won’t start with the windows startup.
B) If you are getting this error message (at your NFS server):
"(rpc.mountd[7243]: refused mount request from 192.168.XX.XX for <mount>: illegal port 24784"
you are most probably trying to connect on port over 1024. To connect to NFS share you need
to have 'insecure' option at your /etc/exports (if missing fix it and run `exportfs -r`)
TIP: The mounting script requires UAC to start the service, if the
service is not started already. You can:1) run it manually - you will see UAC window 2) create a new Task in Task Scheduler and check the check box "Run it with highest privileges" 3) create a startup powershell script in the local policies
Migration from the NFS OR windows share network drive (e.g. using off-line windows functionality) to cloud
Deleting the network drive (in my case an U: drive)
This issue can arise when you have your off-line files functionality switched on and the files are backup to a network drive. If your company changes that in favor of going to some cloud service, it can bring you a deadlock situation in your profile, when some application still need that previous network drive, but you still need to switch to to new cloud provider.
If you are using a NFS Client for windows from Microsoft this is how you get rid of the previous network drive:
As Got rid of the U: drive (not yet the message) with following steps:
1) Go to -> Start MenuProgramsAdministrative ToolsServices for Network File System (NFS)
2) Stop client for NFS with right-clicking on the item and selecting stop service
3) The simple manual removal works!!!!
net use u: /delete
--> U: was deleted successfully.
For the windows to forget the previous drive and correctly set the Volatile Environment to the new configuration you have to reboot.
Getting rid of the error message: Attempting to perform the InitializeDefaultDrives operation on the ‘FileSystem’ provider failed.
The error message does not appear with the Client for NFS stopped. It is enough to have it in state manual and start it via script
@ferventcoder I re-ran the install with -dv and here’s the output (note that I removed some system-specific info, if you need I can re-add it back in):
PS C:WINDOWSsystem32> choco install ruby -dv
Chocolatey v0.9.9.8
Chocolatey is running on Windows v 6.3.9600.0
Attempting to delete file "C:/ProgramData/chocolatey/choco.exe.old".
Attempting to delete file "C:ProgramDatachocolateychoco.exe.old".
Command line: "C:ProgramDatachocolateychoco.exe" install ruby -dv
Received arguments: install ruby -dv
-- SYSTEM SPECIFIC INFO DELETED --
Installing the following packages:
ruby
By installing you accept licenses for the packages.
[NuGet] Installing 'ruby 2.1.6'.
[NuGet] Added file 'chocolateyInstall.ps1' to folder 'rubytools'.
[NuGet] Added file 'ruby.nupkg' to folder 'ruby'.
[NuGet] Successfully installed 'ruby 2.1.6'.
ruby v2.1.6
Contents of 'C:ProgramDatachocolateylibrubytoolschocolateyInstall.ps1':
try {
$packageId = 'ruby'
$binRoot = Get-BinRoot
# $rubyFolder = '187'
# $url = 'http://dl.bintray.com/oneclick/rubyinstaller/rubyinstaller-1.8.7-p374.exe?direct'
# $checksum = '2e33a098f126275f7cb29ddcd0eb9845'
# $rubyFolder = '193'
# $url = 'http://dl.bintray.com/oneclick/rubyinstaller/rubyinstaller-1.9.3-p551.exe?direct'
# $checksum = '25de5ff94b76d7d308cb75ba8179a6c0'
# $rubyFolder = '200'
# $url = 'http://dl.bintray.com/oneclick/rubyinstaller/rubyinstaller-2.0.0-p645.exe?direct'
# $checksum = 'cb25a38508e22a869b48df7974840eb78c77635c'
# $url64 = 'http://dl.bintray.com/oneclick/rubyinstaller/rubyinstaller-2.0.0-p645-x64.exe?direct'
# $checksum64 = '8f8f39d69a222b5472254969755ff5d36dc42585'
$rubyFolder = '21'
$url = 'http://dl.bintray.com/oneclick/rubyinstaller/rubyinstaller-2.1.6.exe?direct'
$checksum = '28aeded17ca34f685fb3fb862fb35ad9414edd05'
$url64 = 'http://dl.bintray.com/oneclick/rubyinstaller/rubyinstaller-2.1.6-x64.exe?direct'
$checksum64 = '07069b095c17f5b108e71951b4f16c410932a02d'
$rubyPath = join-path $binRoot $('ruby' + "$rubyFolder")
$silentArgs = "/verysilent /dir=`"$rubyPath`" /tasks=`"assocfiles,modpath`""
# Install-ChocolateyPackage "$packageId" 'exe' "$silentArgs" "$url" -checksum $checksum
Install-ChocolateyPackage "$packageId" 'exe' "$silentArgs" "$url" "$url64"
#Checksum type sha1 has a bug fixed in 0.9.9.6 - https://github.com/chocolatey/choco/issues/253
#-checksum $checksum -checksumType 'sha1' -checksum64 $checksum64 -checksumType64 'sha1'
$rubyBin = join-path $rubyPath 'bin'
Write-Host "Adding `'$rubyBin`' to the local path"
$env:Path = "$($env:Path);$rubyBin"
# # Install and configure pik
# Write-Host "Now we are going to install pik and set up the folder - so Ruby is pointed to the correct version"
# $nugetBin = join-path $env:ChocolateyInstall 'bin'
# #$gem = 'gem.bat'
# $pikInstall = 'pik_install.bat'
# & gem install pik
# & $pikInstall "$nugetBin"
# & pik add $rubyBin
# & pik use $rubyFolder
} catch {
Write-ChocolateyFailure "$packageId" $($_.Exception.Message)
throw
}
The package ruby wants to run 'chocolateyInstall.ps1'.
Note: If you don't run this script, the installation will fail.
Note: To confirm automatically next time, use '-y' or consider setting
'allowGlobalConfirmation'. Run 'choco feature -h' for more details.
Do you want to run the script?
1) yes
2) no
3) print
1
Calling command ['"C:WINDOWSSystem32WindowsPowerShellv1.0powershell.exe" -NoProfile -NoLogo -ExecutionPolicy Bypass -Command "[System.Threading.Thread]::CurrentThread.CurrentCulture = '';[System.
Threading.Thread]::CurrentThread.CurrentUICulture = ''; & import-module -name 'C:ProgramDatachocolateyhelperschocolateyInstaller.psm1'; & 'C:ProgramDatachocolateyhelperschocolateyScriptRunner.
ps1' -packageScript 'C:ProgramDatachocolateylibrubytoolschocolateyInstall.ps1' -installArguments '' -packageParameters ''"']
Attempting to perform the InitializeDefaultDrives operation on the 'FileSystem' provider failed.
DEBUG: Posh version is 4.0
DEBUG: Loading community extensions
VERBOSE: Exporting function 'Get-BinRoot'.
VERBOSE: Exporting function 'Get-ChecksumValid'.
VERBOSE: Exporting function 'Get-ChocolateyUnzip'.
VERBOSE: Exporting function 'Get-ChocolateyWebFile'.
VERBOSE: Exporting function 'Get-EnvironmentVariable'.
VERBOSE: Exporting function 'Get-EnvironmentVariableNames'.
VERBOSE: Exporting function 'Get-FtpFile'.
VERBOSE: Exporting function 'Get-ProcessorBits'.
VERBOSE: Exporting function 'Get-UACEnabled'.
VERBOSE: Exporting function 'Get-VirusCheckValid'.
VERBOSE: Exporting function 'Get-WebFile'.
VERBOSE: Exporting function 'Get-WebHeaders'.
VERBOSE: Exporting function 'Install-BinFile'.
VERBOSE: Exporting function 'Install-ChocolateyDesktopLink'.
VERBOSE: Exporting function 'Install-ChocolateyEnvironmentVariable'.
VERBOSE: Exporting function 'Install-ChocolateyExplorerMenuItem'.
VERBOSE: Exporting function 'Install-ChocolateyFileAssociation'.
VERBOSE: Exporting function 'Install-ChocolateyInstallPackage'.
VERBOSE: Exporting function 'Install-ChocolateyPackage'.
VERBOSE: Exporting function 'Install-ChocolateyPath'.
VERBOSE: Exporting function 'Install-ChocolateyPinnedTaskBarItem'.
VERBOSE: Exporting function 'Install-ChocolateyPowershellCommand'.
VERBOSE: Exporting function 'Install-ChocolateyShortcut'.
VERBOSE: Exporting function 'Install-ChocolateyVsixPackage'.
VERBOSE: Exporting function 'Install-Vsix'.
VERBOSE: Exporting function 'Install-ChocolateyZipPackage'.
VERBOSE: Exporting function 'Set-EnvironmentVariable'.
VERBOSE: Exporting function 'Start-ChocolateyProcessAsAdmin'.
VERBOSE: Exporting function 'Test-ProcessAdminRights'.
VERBOSE: Exporting function 'Uninstall-BinFile'.
VERBOSE: Exporting function 'Uninstall-ChocolateyPackage'.
VERBOSE: Exporting function 'UnInstall-ChocolateyZipPackage'.
VERBOSE: Exporting function 'Update-SessionEnvironment'.
VERBOSE: Exporting function 'Write-ChocolateyFailure'.
VERBOSE: Exporting function 'Write-ChocolateySuccess'.
VERBOSE: Exporting function 'Write-FileUpdateLog'.
VERBOSE: Exporting alias 'Generate-BinFile'.
VERBOSE: Exporting alias 'Add-BinFile'.
VERBOSE: Exporting alias 'Remove-BinFile'.
DEBUG: Running 'Get-BinRoot'
Get-BinRoot is going to be deprecated by v1. Many packages no longer require it since the folders no longer have versions on them.
DEBUG: Running 'Install-ChocolateyPackage' for ruby with url:'http://dl.bintray.com/oneclick/rubyinstaller/rubyinstaller-2.1.6.exe?direct', args: '/verysilent /dir="C:toolsruby21"
/tasks="assocfiles,modpath"', fileType: 'exe', url64bit: 'http://dl.bintray.com/oneclick/rubyinstaller/rubyinstaller-2.1.6-x64.exe?direct', checksum: '', checksumType: '', checksum64: '',
checksumType64: '', validExitCodes: '0'
DEBUG: Running 'Get-ChocolateyWebFile' for ruby with url:'http://dl.bintray.com/oneclick/rubyinstaller/rubyinstaller-2.1.6.exe?direct',
fileFullPath:'C:UserseadamsAppDataLocalTempchocolateyrubyrubyInstall.exe', url64bit:'http://dl.bintray.com/oneclick/rubyinstaller/rubyinstaller-2.1.6-x64.exe?direct', checksum: '',
checksumType: '', checksum64: '', checksumType64: ''
DEBUG: Running 'Get-ProcessorBits'
DEBUG: CPU is 64 bit
DEBUG: Setting url to 'http://dl.bintray.com/oneclick/rubyinstaller/rubyinstaller-2.1.6-x64.exe?direct' and bitPackage to 64
DEBUG: Running 'Get-WebHeaders' with url:'http://dl.bintray.com/oneclick/rubyinstaller/rubyinstaller-2.1.6-x64.exe?direct', userAgent: 'chocolatey command line'
DEBUG: Setting the UserAgent to 'chocolatey command line'
DEBUG: Request Headers:
DEBUG: 'Accept':'*/*'
DEBUG: 'User-Agent':'chocolatey command line'
DEBUG: Response Headers:
DEBUG: 'Content-Disposition':'attachment;filename="rubyinstaller-2.1.6-x64.exe"'
DEBUG: 'Age':'30098'
DEBUG: 'X-Cache':'Hit from cloudfront,MISS from localhost'
DEBUG: 'X-Amz-Cf-Id':'3OMKJHbXKFDqf6CZWUi-leO6ECM9b9Z6UUvpUgr3CebL_k0lSuzn5w=='
DEBUG: 'X-Cache-Lookup':'MISS from localhost:3128'
DEBUG: 'Connection':'keep-alive'
DEBUG: 'Accept-Ranges':'bytes'
DEBUG: 'Content-Length':'18209758'
DEBUG: 'Content-Type':'application/unknown'
DEBUG: 'Date':'Mon, 06 Jul 2015 13:35:42 GMT'
DEBUG: 'ETag':'"50a2c0097532a4086fa58b6507f6181c"'
DEBUG: 'Last-Modified':'Thu, 16 Apr 2015 19:00:44 GMT'
DEBUG: 'Server':'AmazonS3'
DEBUG: 'Via':'1.1 ae2ec41419bb9b44ca9b925fad50a43f.cloudfront.net (CloudFront), 1.1 localhost (squid)'
DEBUG: ruby's requested file has already been downloaded. Using cached copy at
'C:UserseadamsAppDataLocalTempchocolateyrubyrubyInstall.exe'.
DEBUG: Checking that 'C:UserseadamsAppDataLocalTempchocolateyrubyrubyInstall.exe' is the size we expect it to be.
DEBUG: Verifying package provided checksum of '' for 'C:UserseadamsAppDataLocalTempchocolateyrubyrubyInstall.exe'.
DEBUG: Running 'Get-ChecksumValid' with file:'C:UserseadamsAppDataLocalTempchocolateyrubyrubyInstall.exe', checksum: '', checksumType: ''
DEBUG: Running 'Install-ChocolateyInstallPackage' for ruby with file:'C:UserseadamsAppDataLocalTempchocolateyrubyrubyInstall.exe', args: '/verysilent /dir="C:toolsruby21"
/tasks="assocfiles,modpath"', fileType: 'exe', validExitCodes: '0'
Installing ruby...
DEBUG: Running 'Start-ChocolateyProcessAsAdmin' with exeToRun:'C:UserseadamsAppDataLocalTempchocolateyrubyrubyInstall.exe', statements: '/verysilent /dir="C:toolsruby21"
/tasks="assocfiles,modpath" '
DEBUG: Elevating Permissions and running C:UserseadamsAppDataLocalTempchocolateyrubyrubyInstall.exe /verysilent /dir="C:toolsruby21" /tasks="assocfiles,modpath" . This may take a while,
depending on the statements.
DEBUG: Finishing 'Start-ChocolateyProcessAsAdmin'
ruby has been installed.
Adding 'C:toolsruby21bin' to the local path
Command ['"C:WINDOWSSystem32WindowsPowerShellv1.0powershell.exe" -NoProfile -NoLogo -ExecutionPolicy Bypass -Command "[System.Threading.Thread]::CurrentThread.CurrentCulture = '';[System.Threadin
g.Thread]::CurrentThread.CurrentUICulture = ''; & import-module -name 'C:ProgramDatachocolateyhelperschocolateyInstaller.psm1'; & 'C:ProgramDatachocolateyhelperschocolateyScriptRunner.ps1' -pa
ckageScript 'C:ProgramDatachocolateylibrubytoolschocolateyInstall.ps1' -installArguments '' -packageParameters ''"'] exited with '0'
Calling command ['"shutdown" /a']
Command ['"shutdown" /a'] exited with '1116'
Capturing package files in 'C:ProgramDatachocolateylibruby'
Found 'C:ProgramDatachocolateylibrubyruby.nupkg'
with checksum '0E2737AC542C9491F4C94CFD13C98C9B'
Found 'C:ProgramDatachocolateylibrubytoolschocolateyInstall.ps1'
with checksum 'CF47C0F08CDBB3ADEFD9AE1D33BB38F8'
Attempting to delete file "C:ProgramDatachocolatey.chocolateyruby.2.1.6.sxs".
Attempting to delete file "C:ProgramDatachocolatey.chocolateyruby.2.1.6.pin".
Attempting to delete directory "C:ProgramDatachocolateylib-badruby".
The install of ruby was NOT successful.
Error while running 'C:ProgramDatachocolateylibrubytoolschocolateyInstall.ps1'.
See log for details.
Moving 'C:ProgramDatachocolateylibruby'
to 'C:ProgramDatachocolateylib-badruby'
Chocolatey installed 0/1 package(s). 1 package(s) failed.
See the log for details (C:ProgramDatachocolateylogschocolatey.log).
Failures:
- ruby
Exiting with 1
PS C:WINDOWSsystem32>
Note that the «Attempting to perform the InitializeDefaultDrives operation on the ‘FileSystem’ provider failed.» error came directly after the powershell command.
Thanks for taking a look!
-Eric