Use two deployment types and a requirement that detects whether the D drive is present then.
J From: [email protected] [mailto:[email protected]] On Behalf Of Aday, Karalene B (RCIS) Sent: Tuesday, March 31, 2015 3:09 PM To: [email protected] Subject: [mssms] RE: Ideas on determining where to install software It was a cooperate standard we had to follow that was finally done away with. Unfortunately way to many machines to redo, they will have to be phased out slowly over time. So for now we need to find a reasonable solution. From: [email protected]<mailto:[email protected]> [mailto:[email protected]] On Behalf Of Jason Sandys Sent: Tuesday, March 31, 2015 2:36 PM To: [email protected]<mailto:[email protected]> Subject: [mssms] RE: Ideas on determining where to install software Honestly, get rid of the systems with 2 partitions - they are pointless and cause issues. Non-standardization is the root of many/most issues in IT environments. J From: [email protected]<mailto:[email protected]> [mailto:[email protected]] On Behalf Of Aday, Karalene B (RCIS) Sent: Tuesday, March 31, 2015 1:08 PM To: [email protected]<mailto:[email protected]> Subject: [mssms] FW: Ideas on determining where to install software Looking for some ideas. We currently have Windows 7 and Windows 8.1 in our environment. Some of the Windows 8.1 have 2 partitions some do not. Rather than package everything twice I would like to come up with a script or some type of logic to determine if the partition is present and depending on that where to install the software. Any suggestions or does anyone have a script or something else I could look at to get some ideas? Thank you!
