Jump to content

Recommended Posts

Posted

Hi everyone,

 

We are trying to use VS2017 Community for our Computer Science classes but are having difficulties in getting to save to network drives. We have tried getting students to sign in themselves using their 365 accounts and VS2017 picks up their home directories in UNC format but does not let them save. If we change it to the mapped drive letter of their home drives it works but when you click on browse their home directory has a red cross on it, once you click on this and then click cancel and ok it allows the home drive letter to be used. This is not ideal as they would have to do this every time.

 

We have also tried using psexec to run VS2017 Community as an existing user that has already signed in and set the project locations and the same issue persists, the home drive letter has a red cross on it. Clicking on it and then clicking OK gets it working again.

 

We are not sure why the drive mappings in VS2017 always show as though they are disconnected.

 

We have tried EnableLinkedConnections and a whole host of other things but have had no joy.

 

The OS is Windows 10 Education 1607 64 Bit.

  • 3 weeks later...
Posted

We've rolled out VS 2017 Community to our ICT Suites this year (along with 1703).

I don't recall having any issues saving to our network locations during my own testing and also from testing by students.

I'll have to double check just in case something was missed.

 

We use Folder Redirection on My Documents, but also map the same location in AD using the regular HomeDrive stuff.

  • Thanks 1
Posted
We've rolled out VS 2017 Community to our ICT Suites this year (along with 1703).

I don't recall having any issues saving to our network locations during my own testing and also from testing by students.

I'll have to double check just in case something was missed.

 

We use Folder Redirection on My Documents, but also map the same location in AD using the regular HomeDrive stuff.

 

Exactly how my network is set up, so I'm feeling optimistic.

 

We're moving from 2010 Pro to 2017... Any major differences or issues reported by your ICT teaching staff?

Posted
Exactly how my network is set up, so I'm feeling optimistic.

 

We're moving from 2010 Pro to 2017... Any major differences or issues reported by your ICT teaching staff?

 

Hard to say.

Our upgrade is from VS 2013 Community on our Citrix VDI environment to VS 2017 Community locally installed on the workstations so most of our feedback has been mostly focused on that.

 

The majority of our Students are already using 2017 at home and have been pestering us to upgrade. I'm not expecting any issues.

  • Thanks 1
Posted

I've just tested our setup with a test student and can confirm that I'm seeing no issues with saving projects to UNC/Redirected paths.

VS picks up the HomeShare path fine (our DFS path to the Users HomeShare) and saves without any issues.

  • Thanks 1
Posted (edited)

Would you mind sharing how you've configured your deployment? I have an Application in MDT, but it's not installing. It closes with error 2 in BDD.log if using Response.json for options, and error 0 (successful!) but doesn't install anything when putting all the Workflow switches in the command line.

 

I formed an offline installation using --layout, which installs fine interactively. It's just deployment that doesn't seem to work. I can deploy Office 2016 without issue, so it's not permissions or other task settings; It must be linked to how the task is set up.

 

EDIT: FIXED! Adding the "--wait" switch to the command line forced the vs_setup.exe application to wait for the called installer (a new process) to finish before quitting. Previously vs_setup.exe would close when the installer was launched, which triggered the next task in the MDT task sequence (restart).

Edited by LemonEntry
Added fix
Posted (edited)
Would you mind sharing how you've configured your deployment? I have an Application in MDT, but it's not installing. It closes with error 2 in BDD.log if using Response.json for options, and error 0 (successful!) but doesn't install anything when putting all the Workflow switches in the command line.

 

I formed an offline installation using --layout, which installs fine interactively. It's just deployment that doesn't seem to work. I can deploy Office 2016 without issue, so it's not permissions or other task settings; It must be linked to how the task is set up.

 

EDIT: FIXED! Adding the "--wait" switch to the command line forced the vs_setup.exe application to wait for the called installer (a new process) to finish before quitting. Previously vs_setup.exe would close when the installer was launched, which triggered the next task in the MDT task sequence (restart).

 

Ah nice, I didn't know about the --wait switch. I cheated a threw together a quick AutoIt .exe which called the main installer and then waited for the new process to end before exiting.

 

Run("vs_community.exe --add Microsoft.VisualStudio.Workload.CoreEditor --add Microsoft.VisualStudio.Workload.ManagedDesktop --add Microsoft.VisualStudio.Workload.NativeDesktop --add Microsoft.VisualStudio.Workload.Universal --includeRecommended --passive --norestart")
Sleep(10000)
While ProcessExists("vs_community.exe")
WEnd
Sleep(10000)
While ProcessExists("vs_setup_bootstrapper.exe")
WEnd
Sleep(10000)
While ProcessExists("vs_installershell.exe")
WEnd

Edited by Arcolite
Posted
Users need to sign in? I haven't needed to during testing...!

 

Same, the sign-in box appears, but you can just skip it. It's not required.

  • Thanks 1
Posted (edited)
Yeah you can skip it but it only gives you 30 days license, you have to activate it per user per machine unless it's just Windows 10 being painful Edited by keyboards
  • Thanks 2
Posted
Yeah you can skip it but it only gives you 30 days license, you have to activate it per user per machine unless it's just Windows 10 being painful

 

:scared:

By any chance do you know if it can be registered as part of an O365 education tenancy?

Posted
Users need to sign in? I haven't needed to during testing...!

 

Same, the sign-in box appears, but you can just skip it. It's not required.

 

Example here

 

Visual Studio example.jpg

Posted
:scared:

By any chance do you know if it can be registered as part of an O365 education tenancy?

 

I tested a couple yesterday and it worked, so it looks like you can, which is a bit of a lifesaver, well that's the plan I'm rolling out here.

  • Thanks 1
Posted
I tested a couple yesterday and it worked, so it looks like you can, which is a bit of a lifesaver, well that's the plan I'm rolling out here.

Just tried it myself and it reports it's registered, so here's hoping...

  • Thanks 1
  • 1 month later...
Posted
Hey, This is an interesting thread. Can anyone let me know how the created their json file and how did they install VS community using the command line? I have tried using a json file a student kindly created, but the install keeps failing saying it cannot find the json file. But it keeps looking for the file on the C:\program files location when the json file is on a network share as the program files\vbstudio folder hasn't been created. I am happy to start from scratch using any instructions.
Posted

All I do it put the vs_community.exe onto a VisualStudio share then run the following to pull down the Offline Installation files.

 

"\\domain\dfsnamespace\VisualStudio\vs_community.exe" --layout "\\domain\dfsnamespace\VisualStudio" --add Microsoft.VisualStudio.Workload.CoreEditor --add Microsoft.VisualStudio.Workload.ManagedDesktop --add Microsoft.VisualStudio.Workload.NativeDesktop --add Microsoft.VisualStudio.Workload.Universal --includeRecommended

 

This adds the bulk of the things needed for C# or VB apps.

 

Then to install I then run I have a Post-Installation task in our KACE 2000 Deployment Appliance which maps a drive to that location then runs the exe.

 

net use Z: "\\domain\dfsnamespace\VisualStudio" /USER:domain\readonlyaccount readonlyaccountpassword
Z:\vs_community.exe --add Microsoft.VisualStudio.Workload.CoreEditor --add Microsoft.VisualStudio.Workload.ManagedDesktop --add Microsoft.VisualStudio.Workload.NativeDesktop --add Microsoft.VisualStudio.Workload.Universal --includeRecommended --passive --norestart
net use Z: /DELETE /Y

  • Thanks 1
Posted
Thanks Arthur. Python will install if I run the install as a separate script. If I try to run the install script with the python line added. It doesn't run. If you've got one script which installs python and the rest of the stuff, please let me have it - thanks
Posted
If I try to run the install script with the python line added. It doesn't run.

Did you update your 'layout' folder first so that it contains the relevant Python files? e.g.

 

vs_community.exe --layout "\\domain\dfsnamespace\VisualStudio" --add Microsoft.VisualStudio.Workload.CoreEditor --add Microsoft.VisualStudio.Workload.ManagedDesktop --add Microsoft.VisualStudio.Workload.NativeDesktop --add Microsoft.VisualStudio.Workload.Universal [color="#FF0000"]--add Microsoft.VisualStudio.Workload.Python[/color] --includeRecommended --lang en-US

 

https://docs.microsoft.com/en-us/visualstudio/install/install-vs-inconsistent-quality-network#step-2---create-a-local-install-cache

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now



×
×
  • Create New...