Change Q drive to another letter
Hi,
Does anyone have any experience of changing the Q drive to another drive?
We already use the Q drive in our company. Has anyone tried changing it? Does it work with no problems, or does it require more work? Are there any problems that we will meet down the road by doing this?
We havn't sequenced any applications yet, and plan on using SCCM 2007 to deploy them.
Thanks.
Does anyone have any experience of changing the Q drive to another drive?
We already use the Q drive in our company. Has anyone tried changing it? Does it work with no problems, or does it require more work? Are there any problems that we will meet down the road by doing this?
We havn't sequenced any applications yet, and plan on using SCCM 2007 to deploy them.
Thanks.
0 Comments
[ + ] Show comments
Answers (6)
Please log in to answer
Posted by:
pjgeutjens
13 years ago
We already use the Q drive in our company
It does not actually have to be Q per se, I'd just advise you to be consistent in which drive letter you use, so if you use R:, every sequencer uses R:
PJ
Posted by:
Rheuvel
13 years ago
Also have a look here, this is about all the documentation there is: http://blogs.technet.com/b/appv/archive/2010/02/23/app-v-4-6-documentation-now-available-on-technet.aspx
It will tell you how and where to change the driver letter for the sequencer, client, etc... And all else you need to know.
It will tell you how and where to change the driver letter for the sequencer, client, etc... And all else you need to know.
Posted by:
JimmyG
13 years ago
Thanks. I have already managed to get it working using V drive instead. I was just wondering if anyone had any real world experience with running App-V on another drive. I just want to make sure that I am not hit with some unexpected surprises down the road.
[font="courier new"]
[font="courier new"]
Posted by:
kkaminsk
13 years ago
Just don't change the drive letter after sequencing and deploying your applications. You can change the driver letter later on but...
Registry values and file pointers will change but if you have file pointers say inside a propietary file such as a .dat file App-V won't catch that and change it to suit the new environment. This esstentially means that you have the potential to break some of your virtual applications as part of that change.
Registry values and file pointers will change but if you have file pointers say inside a propietary file such as a .dat file App-V won't catch that and change it to suit the new environment. This esstentially means that you have the potential to break some of your virtual applications as part of that change.
Posted by:
ksaunam
13 years ago
I was just wondering if anyone had any real world experience with running App-V on another drive. I just want to make sure that I am not hit with some unexpected surprises down the road.
I have, or at least from one of our customers back then, experience on running on "non-standard" drive letter. As far as I can tell, there is absolutely no issues with that given that all clients (this was TS environment so less App-V Clients) use the same settings and sequencing machines too.
br,
Kalle
Posted by:
JimmyG
13 years ago
I have, or at least from one of our customers back then, experience on running on "non-standard" drive letter. As far as I can tell, there is absolutely no issues with that given that all clients (this was TS environment so less App-V Clients) use the same settings and sequencing machines too.
br,
Kalle
Thanks a lot. Its reassuring to know that we are not the first/only ones
Jimmy [:)]
Rating comments in this legacy AppDeploy message board thread won't reorder them,so that the conversation will remain readable.