pbalderos

Hello Community! So, the world was just asked of me (as with all IT folks). We have about 200 users we think have 2 applications installed on their computer we will call SAPGUI and SAPSLC. I was asked to run a report that will show which users have the applications installed on their computer. Here is the problem: I was only given a spreadsheet with employees username (ex. jthomas) which by the way have were all discovered in SCCM after running AD User Discovery. I haven't used much reporting and have limited use on quries until, well now. *sigh Any idea how I can accomplish this?

Hi Mashood! Thanks for the reply. I haven't tried to create a another package but am planning on it. Could you point me to the location of the following? 1) Location of updates on target device 2) Locations of updates package on distribution point

Hello Community Peeps! Hoping someone could help me out. I started working at this company who has an Windows Updates Automatic deployment Rule Configured to create a update package after patch Tuesday. I last enabled it to deploy updates back in May and everything went fine. From what I can remember all I did was right click enabled and it kicked off on schedule. Well yesterday 08/18/2017 at 4:30 CST I set the "Software Available Time" for 08/19/2017 12:00 am and the "Installation deadline" for 08/19/2017 5:00 am and enabled it right before I left work. This was a last minute change because I was requested to deploy updates a couple days before. Could there be some additional pushing to a DP that I need to do? I thought this was also specified when you first create the Automatic Deployment Rule: Got home about an hour later and logged into some of the servers to see if anything happened. Nothing. I also ran the following reports: Compliance 1 - Overall Compliance States 1 - Enforcement State for a Deployment Looking at the properties of the deployment I can tell you the following about the configuration: 1) It creates updates group of security patches for servers only 2) It schedules deployment based on Client local time since this is a global company 3) It points it to a collection that has all of our servers

Yes. I did distribute to the DPs. I am going to updates the DP and try again.

Hello All. I am trying to image to a laptop in SCCM. It all of the way to the 'Install Image' of the process and it fails. During this time I had the smsts.log just to see where it exactly where it stops. As you can see in the screen shot it halts at "ZTI Deployment failed, Return Code = - 2147024894 0x80070002". Also, below is a little list other info that might be useful. - I built this task seq using the MDT SCCM Integrated task sequence. - The image was build with a VM in hyper-v using MDT 2013 Update1 to create the WIM - I exported the wim to SCCM for deployment - I have not made any custom edits to the task seq or its variables. I attached a pic of the point in which it fails in the log and also the status page Thanks in advance

Hello all I am working on testing a deployment of Windows 10 for my company but seem to have hit a wall. I Created Windows 10 image using MDT I Imported Image into SCCM 2012 R2 SP1 The image kicks off with no issue but half way through it gives an error "Failed Task Seq" and then it counts down to restart. I looked at all of the log files especially the SMSTS.log and they all look clean with no errors. Here are the log files I polled from the systems I attempted to image. Am I missing something? I didn't make any changes to the SCCM task seq as I wanted to give it a run without any customizations made. https://onedrive.live.com/redir?resid=396947B01718D115!393&authkey=!ADJAxXHM-4xW4DM&ithint=folder%2clog

ISSUE RESOLVED!! It looks like the ISO was bad. I downloaded the ISO again and deleted the OS sources from MDT and copied over a fresh copy from the new download. Everything worked from start to finish.

Hello All, I recently installed MDT 2013 Update 1, as I am trying to build and capture a Windows 10x64 Ent ref image. I followed the guide (link below) to a T and it keeps failing right in the middle of "Installing Operating System". I tried this at home and at work and it failes the same way, same error.https://technet.microsoft.com/en-us/library/mt297533(v=vs.85).aspx Any help would be appreciated. I tried to make sense of the logs as much as possible and rechecked everything I did and it all looks correct. Also here is a link to the following logs: BDD.log, SMSTS.log, LiteTouch.log. I also uploaded them as attachments. https://onedrive.live.com/redir?resid=396947B01718D115!192&authkey=!ANuf33N56tQ5r9w&ithint=folder%2c BDD.LOG LiteTouch.log smsts.log

As recommended by a lot of SCCM experts I am creating a Win 8.1 reference image using MDT 2013. When I boot my reference VM using the MDT Build Lab x64.iso it gets stuck at "Processing Rules" as pictured below: This is what my Rules look like: [settings] Priority=Default [Default] _SMSTSORGNAME=Death Star Enterprises UserDataLocation=NONE DoCapture=YES OSInstall=Y AdminPassword=P@ssw0rd TimeZoneName=Central Standard Time JoinWorkgroup=WORKGROUP HideShell=YES FinishAction=SHUTDOWN DoNotCreateExtraPartition=YES WSUSServer=http://hv-host2.wolf.local:8530 ApplyGPOPack=NO SLSHARE=\\HV-Host2\Logs$ SkipAdminPassword=YES SkipProductKey=YES SkipComputerName=YES SkipDomainMembership=YES SkipUserData=YES SkipLocaleSelection=YES SkipTaskSequence=NO SkipTimeZone=YES SkipApplications=YES SkipBitLocker=YES SkipSummary=YES SkipRoles=YES SkipCapture=NO SkipFinalSummary=YES And in the Bootstrap.ini file this is how I have it configured [settings] Priority=Default [Default] DeployRoot=\\HV-Host\MDTBuildLab$ UserDomain=Wolf UserID=MDT_BA UserPassword=P@ssw0rd SkipBDDWelcome=YES

T Thanks again h4xor, Under the task: Install>Set Variable for Drive Letter I changed the OSDPreserveDriveLetter value to "True" and reimaged the computer and C: became the primary I also went into each of the Format and Partition Disk (UEFI, 6.1 and 6.0) tasks and made sure all of the Volumes except Local Disk (Primary) was set to "Do not assign a drive letter to this partition". Now the only things I am trying to fix is changing the C: drive label from OSDisk to Local Disk (C:) I would like to keep it "traditional" My actions: I changed the Partition Name as shown in the screen shot below to from OSDisk to Local Disk. This is the only thing that didn't change. Any thoughts on that one?

Yup it is set to False. Once I am finished reading the link you sent me I am going to change it. I just want to see what other info I can gather in addition.

h4x0r Here are the smsts.logs from my successful Windows 8.1 image deployment smsts.log smsts-20150830-182755.log

Sure I upload it tonight! Thanks for link also!

On the windows 7 computer it was E: on the Windows 8.1 it was D:

Thanks again, I was able to run the fill image with no errors. I followed one of the steps you recommended. Under Install>Apply Operating System Image: Properties Tab> Select the location where you want to apply this operating system I changed the option to "Next available formatted partition". The only thing I need to correct is that it is installing to the D: driver letter so I need to fix this. I think that was defined in the UDI Designer that I am using for this image. But I am happy to get the image install at this point. Thanks for all of your help I really appreciate it.