If this is your first visit, be sure to check out the FAQ by clicking the link above. You may have to register before you can post: click the register link above to proceed. To start viewing messages, select the forum that you want to visit from the selection below. |
|
|
Thread Tools | Display Modes |
#1
|
|||
|
|||
MSP Regfile reverted by SP2
We roll out our office 2007 Pro by putting one .msp customized install in the
Updates folder and then we update it to SP2 by putting the SP2 .msp files in that same updates folder. Here is my issue.... We are shutting off sandbox mode by changing the sandbox mode registry entry to 2. (I have added this registry entry into the reg section of my custom install .msp.) We need to do this because of some legacy databases that can't run reports if the sandbox mode is enabled. We know that the code can be run differently, but the people in charge of those particular databases aren't in a position to fix that right now. What happens is sandbox mode gets turned back on once SP2 rolls after the install. We could then push a reg file to turn it off again, but we are running both 2002 and 2007 databases at this time and every time you go between the old and the new, that small install happens. That uses the cashed install on the C:\ drive and turns Sandbox mode back on. My question is: What do we do to keep Sandbox mode disabled? Is there a way to truly slip stream SP2 so that the Customization file affects SP2 and then it wouldn't run as an update and turn sandbox mode back on? Any suggestions you might have would be hugely appreciated! Thank you in advance for your time! |
#2
|
|||
|
|||
MSP Regfile reverted by SP2
Bump
"KAReilly" wrote: We roll out our office 2007 Pro by putting one .msp customized install in the Updates folder and then we update it to SP2 by putting the SP2 .msp files in that same updates folder. Here is my issue.... We are shutting off sandbox mode by changing the sandbox mode registry entry to 2. (I have added this registry entry into the reg section of my custom install .msp.) We need to do this because of some legacy databases that can't run reports if the sandbox mode is enabled. We know that the code can be run differently, but the people in charge of those particular databases aren't in a position to fix that right now. What happens is sandbox mode gets turned back on once SP2 rolls after the install. We could then push a reg file to turn it off again, but we are running both 2002 and 2007 databases at this time and every time you go between the old and the new, that small install happens. That uses the cashed install on the C:\ drive and turns Sandbox mode back on. My question is: What do we do to keep Sandbox mode disabled? Is there a way to truly slip stream SP2 so that the Customization file affects SP2 and then it wouldn't run as an update and turn sandbox mode back on? Any suggestions you might have would be hugely appreciated! Thank you in advance for your time! |
Thread Tools | |
Display Modes | |
|
|