Vista jobs

Is anyone even using the DS with Vista?

We are trying to, but we are running into problems at every turn. We haven't converted alot of users to it yet, but we are getting ready to deploy to a few remote machines. We cant even get the images to deploy right, let alone push applications beyond that.

Hello Travis,

I have been using Vista along with DS 6.9 SP1. It works a world better than the origial 6.9 release. what kind issues are you seeing?

Incorrect function usually happen when executing 32 bit app in 64 one or viceversa. Could it be that the scripts need to account for the architecture type?

We use conditions to verify which OS is in use and which Bit per os. So XP 32 uses a different job/task then XP 64 and same goes for vista 32 and 64. So to start with an easy one, Symantec install. There is a different install for each version. The install is a distrubute software task specifically for that OS/Bit. Which still returns Fatal error during installation. Most of our scripts to do installs using Wise scripts which have the detection in them and while they have not specifically been tested with vista they get the Incorrect function. Another oddity is when trying to run a job that works for XP it returns a Logon failure. I have tried fixing the username in the job but still get the same problem.

For some of the jobs I think you might be right in the compatibility issue, I will check into that.

Just to add to the strangness of deploying to Vista, I tried running a job as a different user then the one logged in and the install job would not complete (a script job that is told to run the install). I then changed it to use the Default (local system account) which came back with Incorrect function. Finally I changed it to use the specific user of the user that was logged in. Install popped up and installed correctly.

Am I going to have to force an autologging and use that user to do all my installs?

We get the Windows Boot Manager telling us that winload.exe is corrupt. Same issue with Server 2008. If you drop a cd in and repair the MBR its fine. We have tried numerous platforms, we can pick up the image just fine, then try to deploy it to the same system and it somehow hoses winload.exe. We are on DS 6.9, not SP1. So I will have my team set up an RFC to upgrade to SP1, maybe that will help.

I have the same problem with Vista images. I did a repair and it worked just fine. I do have 6.9 sp1 so that will not fix your issue. I might try using ghost instead to see if it is just an issue with rdeploy. I also tried using the deployanywhere but that did not help either.

Do you repair each one every time you deploy a system? Or is there a way to just inject a 'good' .exe there to avoid the repair?

Ideally we want to be able to deploy workstations and servers without having to then repair the boot loader on every one of them.

We dont have any plans to deploy Vista, I am just doing some testing and noticed the problem and did a repair to it fixed it. I would be currious to how to fix this though. I might end up trying Ghost instead to see if that helps at all.

Yeah Microsoft introduced Windows Service and Process Isolation. check http://www.winsupersite.com/showcase/winvista_secu... for information about the levels of integration. Executing jobs using the local system account works, however, no GUI will be displayed. There is not user intervention at this point and if the job expect user interaction u might see what u are describing.

Nelo