Jump to content

Recommended Posts

Posted

I'm just starting to load some applications in to my new MDT server but i've noticed they aren't deploying. th e3 things we are trying to deploy are office 365, sophos endpoint and papercut. Office 365 appears to be installing fine from the deployment share however sophos and papercut refuse point blank to install. The error logs just give error code 3. They are placed in exactly the same way as the office application in the deployment share and the install commands work when run manually. Also the commands that i'm using are the same as another school in our trust are using.

I'm completely at a loss. I've tried share permissions and changing who the TS is run as but none seem to have any affect.

It's defying logic that one should work and the other's don't.

Does anyone have any experience of this behavior or able to point me in a direction that can help me diagnose it?

Posted
Does it make any difference if the pc doesn't actually log on? When the TS starts up after the OS install, it stays at the login screen. It is installing office whilst it's in that state as i can watch it through the monitor tab.
Posted
so just tried to log in while it was mid TS and it says another user is connected so it must be logged in, just not showing me the session. At the end of my TS i've got a GP update /force and then a reboot. (this is just to make sure it's got everything when it recovered from the domain.
Posted
i'm testing it on a vm so i can log in directly but it appears like it's in a remote session. (Asks me if i want to disconnect the user). Just whilst i've been posting this, i moved the papercut application to another server and tried installing it with remote files rather than on MDT and it installed. So it's interesting it won't install from the mdt server but will another, and office does work from the usual deployment share
Posted

Is MDT similar to MCM (SCCM) when creating packages?

 

Have you got it set to deploy from a TS?

 

Can’t remember where the tick is as not at my desk at the moment.

Posted
It doesn't show a run as in application install tasks, but i notice you are using a run command task. Do they run better from that than the app install task?

 

I found that yes, call a batch command to a central installer, then you can customise as you wish, so the Sophos one for example is:

 

@echo off

SET MCS_ENDPOINT=Sophos\Management Communications System\Endpoint\McsClient.exe

IF "%PROCESSOR_ARCHITECTURE%" == "x86" GOTO X86_PROG

IF NOT EXIST "%ProgramFiles(x86)%\%MCS_ENDPOINT%" GOTO INSTALL

exit /b 0

 

:X86_PROG

IF NOT EXIST "%ProgramFiles%\%MCS_ENDPOINT%" GOTO INSTALL

exit /b 0

 

:INSTALL

pushd \\[sERVER]\SophosAV\

SophosSetup.exe --quiet

Popd

 

The deployment will popup a CMD window with the old 'Jurassic Park' blinking cursor, but will continue once the script finishes.

Posted
Jumping back to this thread, i now think there is a bigger issue at play. ATM we are using windows 10 and 11 images. So office is installed by a prebuilt application (as all the guides show) and deploys in windows 10. Today i've added that application to the same place in the windows 11 TS and imaged a pc and it doesn't work. the CMD flashes up for a second or 2 then disappears. It then continues the TS.

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...