Quantcast
Channel: Configuration Manager 2012 - Operating System Deployment forum
Viewing all 9126 articles
Browse latest View live
↧

Wdf01000.sys BSOD on shutdown after imaging

November 12, 2014, 2:14 pm
$
0
0

We have SCCM 2012 R2 and Dell.  Using the latest combo drivers on Dell, imaging Win7 x86/x64.

I've been seeing BSOD on shutdown on almost all desktops/laptops. They don't BSOD every time, maybe 20-30% of the time on 5-10% of all desktops/laptops.

Dump is below.


Microsoft (R) Windows Debugger Version 6.3.9600.17298 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [C:\Users\katiecc\Downloads\e7440_111214-8330-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available


************* Symbol Path validation summary **************
Response                         Time (ms)     Location
Deferred                                       SRV*http://msdl.microsoft.com/download/symbols
Symbol search path is: SRV*http://msdl.microsoft.com/download/symbols
Executable search path is: 
Windows 7 Kernel Version 7601 (Service Pack 1) MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7601.18526.amd64fre.win7sp1_gdr.140706-1506
Machine Name:
Kernel base = 0xfffff800`0305f000 PsLoadedModuleList = 0xfffff800`032a2890
Debug session time: Wed Nov 12 13:49:33.070 2014 (UTC - 8:00)
System Uptime: 0 days 0:07:08.907
Loading Kernel Symbols
...............................................................
................................................................
...........................................
Loading User Symbols
Loading unloaded module list
............
*******************************************************************************
*                                                                            *
*                        Bugcheck Analysis                                    *
*                                                                            *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 1000007E, {ffffffffc0000005, fffff88000ec6cce, fffff8800a993308, fffff8800a992b60}

*** WARNING: Unable to verify timestamp for TeeDriverx64.sys
*** ERROR: Module load completed but symbols could not be loaded for TeeDriverx64.sys
Probably caused by : TeeDriverx64.sys ( TeeDriverx64+fc0d )

Followup: MachineOwner
---------

3: kd> !analyze -v
*******************************************************************************
*                                                                            *
*                        Bugcheck Analysis                                    *
*                                                                            *
*******************************************************************************

SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M (1000007e)
This is a very common bugcheck.  Usually the exception address pinpoints
the driver/function that caused the problem.  Always note this address
as well as the link date of the driver/image that contains this address.
Some common problems are exception code 0x80000003.  This means a hard
coded breakpoint or assertion was hit, but this system was booted
/NODEBUG.  This is not supposed to happen as developers should never have
hardcoded breakpoints in retail code, but ...
If this happens, make sure a debugger gets connected, and the
system is booted /DEBUG.  This will let us see why this breakpoint is
happening.
Arguments:
Arg1: ffffffffc0000005, The exception code that was not handled
Arg2: fffff88000ec6cce, The address that the exception occurred at
Arg3: fffff8800a993308, Exception Record Address
Arg4: fffff8800a992b60, Context Record Address

Debugging Details:
------------------


EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s.

FAULTING_IP: 
Wdf01000!FxIoQueue::CancelForQueue+252
fffff880`00ec6cce 4c897038        mov     qword ptr [rax+38h],r14

EXCEPTION_RECORD:  fffff8800a993308 -- (.exr 0xfffff8800a993308)
ExceptionAddress: fffff88000ec6cce (Wdf01000!FxIoQueue::CancelForQueue+0x0000000000000252)
   ExceptionCode: c0000005 (Access violation)
  ExceptionFlags: 00000000
NumberParameters: 2
   Parameter[0]: 0000000000000001
   Parameter[1]: 0000000000000038
Attempt to write to address 0000000000000038

CONTEXT:  fffff8800a992b60 -- (.cxr 0xfffff8800a992b60;r)
rax=0000000000000000 rbx=fffffa800cb2de50 rcx=fffffa80109c1500
rdx=0000000075657500 rsi=0000000000000000 rdi=fffffa80109c14a0
rip=fffff88000ec6cce rsp=fffff8800a993540 rbp=fffffa8010a59d30
 r8=0000000000001000  r9=fffff88000e45160 r10=000000000000000c
r11=0000000000000000 r12=fffff88000edad40 r13=0000000000000301
r14=0000000000000000 r15=0000000000000001
iopl=0         nv up ei ng nz na po nc
cs=0010  ss=0018  ds=002b  es=002b  fs=0053  gs=002b             efl=00010286
Wdf01000!FxIoQueue::CancelForQueue+0x252:
fffff880`00ec6cce 4c897038        mov     qword ptr [rax+38h],r14 ds:002b:00000000`00000038=????????????????
Last set context:
rax=0000000000000000 rbx=fffffa800cb2de50 rcx=fffffa80109c1500
rdx=0000000075657500 rsi=0000000000000000 rdi=fffffa80109c14a0
rip=fffff88000ec6cce rsp=fffff8800a993540 rbp=fffffa8010a59d30
 r8=0000000000001000  r9=fffff88000e45160 r10=000000000000000c
r11=0000000000000000 r12=fffff88000edad40 r13=0000000000000301
r14=0000000000000000 r15=0000000000000001
iopl=0         nv up ei ng nz na po nc
cs=0010  ss=0018  ds=002b  es=002b  fs=0053  gs=002b             efl=00010286
Wdf01000!FxIoQueue::CancelForQueue+0x252:
fffff880`00ec6cce 4c897038        mov     qword ptr [rax+38h],r14 ds:002b:00000000`00000038=????????????????
Resetting default scope

CUSTOMER_CRASH_COUNT:  1

PROCESS_NAME:  System

CURRENT_IRQL:  0

ERROR_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s.

EXCEPTION_PARAMETER1:  0000000000000001

EXCEPTION_PARAMETER2:  0000000000000038

WRITE_ADDRESS: GetPointerFromAddress: unable to read from fffff8000330c100
GetUlongFromAddress: unable to read from fffff8000330c1c0
 0000000000000038 Nonpaged pool

FOLLOWUP_IP: 
TeeDriverx64+fc0d
fffff880`05117c0d ??              ???

BUGCHECK_STR:  0x7E

DEFAULT_BUCKET_ID:  NULL_CLASS_PTR_DEREFERENCE

ANALYSIS_VERSION: 6.3.9600.17298 (debuggers(dbg).141024-1500) amd64fre

LAST_CONTROL_TRANSFER:  from fffff88000ec665b to fffff88000ec6cce

STACK_TEXT:  
fffff880`0a993540 fffff880`00ec665b : fffffa80`109c14a0 fffff880`0a993600 00000000`00000000 fffffa80`109c14a0 : Wdf01000!FxIoQueue::CancelForQueue+0x252
fffff880`0a9935b0 fffff880`00eb33d3 : 00000000`00000000 fffffa80`109c14a0 0000057f`ef63eb58 00000000`00001003 : Wdf01000!FxIoQueue::QueuePurge+0x28f
fffff880`0a993630 fffff880`05117c0d : fffffa80`109c14a0 fffffa80`109912d0 fffff880`0511c028 fffff880`0511c028 : Wdf01000!imp_WdfIoQueuePurge+0x10b
fffff880`0a993690 fffffa80`109c14a0 : fffffa80`109912d0 fffff880`0511c028 fffff880`0511c028 fffffa80`109901e0 : TeeDriverx64+0xfc0d
fffff880`0a993698 fffffa80`109912d0 : fffff880`0511c028 fffff880`0511c028 fffffa80`109901e0 fffff880`00e64e1a : 0xfffffa80`109c14a0
fffff880`0a9936a0 fffff880`0511c028 : fffff880`0511c028 fffffa80`109901e0 fffff880`00e64e1a fffffa80`109912d0 : 0xfffffa80`109912d0
fffff880`0a9936a8 fffff880`0511c028 : fffffa80`109901e0 fffff880`00e64e1a fffffa80`109912d0 fffff880`0510f0d8 : TeeDriverx64+0x14028
fffff880`0a9936b0 fffffa80`109901e0 : fffff880`00e64e1a fffffa80`109912d0 fffff880`0510f0d8 fffffa80`109912d0 : TeeDriverx64+0x14028
fffff880`0a9936b8 fffff880`00e64e1a : fffffa80`109912d0 fffff880`0510f0d8 fffffa80`109912d0 00000000`00000000 : 0xfffffa80`109901e0
fffff880`0a9936c0 fffff880`00e58288 : fffffa80`109901e0 00000000`00000000 00000000`00000005 fffff880`0a9937d8 : Wdf01000!FxPkgPnp::NotifyResourceObjectsDx+0x4a
fffff880`0a993730 fffff880`00e64e99 : 00000000`00000000 fffff880`0a9938b0 fffff880`00edb200 fffffa80`109901e0 : Wdf01000!FxPkgPnp::PowerGotoDxIoStopped+0x120
fffff880`0a993780 fffff880`00e5b0f8 : 00000000`0000031c fffff880`0a9938b0 00000000`ffff7fff fffffa80`109901e0 : Wdf01000!FxPkgPnp::PowerGotoDNotZeroIoStopped+0x9
fffff880`0a9937b0 fffff880`00e5ada6 : fffff880`00edb1c0 fffffa80`10990398 fffffa80`109901e0 fffffa80`109901e0 : Wdf01000!FxPkgPnp::PowerEnterNewState+0x1d8
fffff880`0a993910 fffff880`00e5b627 : 00000000`00000000 fffff880`0a9939f0 fffffa80`10990380 fffffa80`109901e0 : Wdf01000!FxPkgPnp::PowerProcessEventInner+0x13e
fffff880`0a993980 fffff880`00e65dd3 : 00000000`00000000 fffffa80`109901e0 00000000`00000000 00000000`00000000 : Wdf01000!FxPkgPnp::PowerProcessEvent+0x1b3
fffff880`0a993a20 fffff880`00e476f2 : 00000000`00000002 0000057f`ef66efd8 fffffa80`109a8bb0 fffffa80`12b46402 : Wdf01000!FxPkgFdo::DispatchDeviceSetPower+0x117
fffff880`0a993a70 fffff880`00e4679a : fffffa80`12b46410 fffffa80`12b46410 fffffa80`12b46410 00000000`00000000 : Wdf01000!FxPkgPnp::Dispatch+0x2aa
fffff880`0a993ad0 fffff880`00e46866 : fffffa80`12b46410 00000000`00000000 fffffa80`109a8bb0 fffffa80`109a8bb0 : Wdf01000!FxDevice::Dispatch+0x19a
fffff880`0a993b10 fffff800`031f0eb5 : 00000000`00000001 00000000`00000000 fffffa80`109a8bb0 fffffa80`12b464b8 : Wdf01000!FxDevice::DispatchWithLock+0xa6
fffff880`0a993b50 fffff800`0337073a : ffffffff`fa0a1f00 fffffa80`1235ab50 00000000`00000080 fffff8a0`00000002 : nt!PopIrpWorker+0x3c5
fffff880`0a993c00 fffff800`030c58e6 : fffff800`0324fe80 fffffa80`1235ab50 fffffa80`13004b50 fffffa80`13b9f010 : nt!PspSystemThreadStartup+0x5a
fffff880`0a993c40 00000000`00000000 : fffff880`0a994000 fffff880`0a98e000 fffff880`0a9932e0 00000000`00000000 : nt!KxStartSystemThread+0x16


SYMBOL_STACK_INDEX:  3

SYMBOL_NAME:  TeeDriverx64+fc0d

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: TeeDriverx64

IMAGE_NAME:  TeeDriverx64.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  51d31e10

STACK_COMMAND:  .cxr 0xfffff8800a992b60 ; kb

FAILURE_BUCKET_ID:  X64_0x7E_TeeDriverx64+fc0d

BUCKET_ID:  X64_0x7E_TeeDriverx64+fc0d

ANALYSIS_SOURCE:  KM

FAILURE_ID_HASH_STRING:  km:x64_0x7e_teedriverx64+fc0d

FAILURE_ID_HASH:  {c079e5d7-83f0-230c-5936-8e6123aa32cd}

Followup: MachineOwner
---------

↧
Search

Build and capture task sequence stops after apply windows updates

November 13, 2014, 8:16 am
$
0
0

Hi

SCCM 2012 SP1 CU4. Deploying Windows 7 SP1.

Pulling my hair out over this one. I successfully performed a build and capture installing some applications. When I choose to install Windows updates, the updates install, the system reboots then doesn't continue. Applications don't install, image isn't captured.

I've tired using the default B&C TS and receive the same results. I've amended the TS to as follows, as suggested in a technet forum post: https://social.technet.microsoft.com/Forums/en-US/a535e509-fc6a-483c-bf24-7e2aa064e5b7/deploying-100-of-available-software-updates-during-a-task-sequence?forum=configmanagerosd

Looking at smsts.log there's errors relating to not accepting the license agreement, but I didn't think this would stop the TS. 

Can someone point out why the deployment stops?

https://dl.dropboxusercontent.com/u/23479177/smsts-20141113-182413.log 

Cheers

↧
↧

SCCM 2012R2 PXE via IpHelper

November 17, 2014, 5:03 am
$
0
0

Hi Everyone,

I'm trying to deploy SCCM2012R2 task sequence via PXE with IpHelpers.

I've configured the IPHelpers to point to the SCCM DP PXE and the DHCP, but nothing happen.

Has someone a quick guide on how to configure SCCM2012 and iphelper?

↧

Staging fails with x64 WinPE on windows 8.1 Update

November 20, 2014, 4:41 am
$
0
0

Hi,

I am facing issue in staging x64 boot file on windows 8.1 Update. It is config manager 2012 R2.

I know there is some issues staging boot files (32 and 64 bit both) on windows XP but do we have any issues related to boot files not working on windows 8.1 update 1 also?

I have created TS that will take usmt and then redeploy 8.1 update. TS starts and perform USMT backup but fails at staging the boot files. Pl. find screen shot as below..

Regards,

↧

Running Post OS Task Sequence on startup

November 20, 2014, 1:41 am
$
0
0

I'm trying to create a rapid deployment solution for our server OS, but I'm not sure how to run a post-os task sequence on boot. 

We use VMWare so what I'm trying to do is create a template from a sysprepped image, then when the machine is cloned and started up it runs a task sequence on boot to apply the new computer name and network settings automatically. So far I have scripted this so that after the template is cloned, a new computer resource is created in SCCM with the MAC address of the new VM and that computer is added to a device collection that has the post os task sequence deployed. But I'm stuck on how to get to run this on boot. 

If I run litetouch.vbs manually on the new computer I don't see the advertised task sequence, but I take it this is because the computer has the same name as the image created by the initial task sequence that installed the OS and config manager. 

So can anybody help me on what the best way to go about this is? Cheers!

↧
↧

.ps1 script does nothing

November 20, 2014, 6:11 am
$
0
0

I have a file (test.ps1) that I try to run and the command immediately returns with no errors. It just seems to do nothing. When I execute the statements individually, line by line, that are in the file I get the output that I expect. I have run 'set-exceutionpolicy Unrestricted' and when I run 'get-executionpolicy' I can confirm that the policy is indeed set. I am running the command as ./test.ps1 from the Windows PowerShell Console. What am I doing wrong?

Thank you.

Kevin

Kevin Burton

↧

Booting from PXE - 0xc0000098 error

October 28, 2014, 2:18 am
$
0
0

Hi everyone,

I've enabled PXE on my DP, configured boot server host name and boot file name DHCP server, imported a computer (actually a VM) to Configurtaion Manager and started to deploy Windows 7. I got error 0xc0000098 - "The Boot Configuration Data (BCD) file from the PXE server does not contain a valid operating system entry. SMSPXE.log:

cannot connect with winhttp; 80072ee5SMSPXE10/28/2014 12:00:10 PM2308 (0x0904)
Failed to get information for MP: . 80072ee5. SMSPXE10/28/2014 12:00:10 PM2308 (0x0904)
PXE::MP_InitializeTransport failed; 0x80004005 SMSPXE10/28/2014 12:00:10 PM2308 (0x0904)
PXE::MP_LookupDevice failed; 0x80004005SMSPXE10/28/2014 12:00:10 PM2308 (0x0904)
cannot connect with winhttp; 80072ee5SMSPXE10/28/2014 12:00:10 PM2308 (0x0904)
Failed to get information for MP: . 80072ee5. SMSPXE10/28/2014 12:00:10 PM2308 (0x0904)
PXE::MP_InitializeTransport failed; 0x80004005 SMSPXE10/28/2014 12:00:10 PM2308 (0x0904)
PXE::MP_ReportStatus failed; 0x80004005SMSPXE10/28/2014 12:00:10 PM2308 (0x0904)
PXE Provider failed to process message. 
Unspecified error (Error: 80004005; Source: Windows)SMSPXE10/28/2014 12:00:10 PM2308 (0x0904)
00:15:5D:05:82:03, 07E3B158-B17C-47DA-88B0-CECD31EF5A8C: Not serviced.SMSPXE10/28/2014 12:00:10 PM2308 (0x0904)

My distribution point works as HTTPS DP and has self-signed certificate; I've read that this configuration is unsupported and I should use the certificate from CA, not self-signed certificate.

So, I've exported the certificate that was used for IIS on DP, pointed SCCM to them, but.. still the same error.

Which certificate should I actually use?

↧

Linux Deployment Guide

November 20, 2014, 6:37 am
$
0
0
Hello everyone.

Ineed helptodeployubuntuwithOSDSccm2012.

I wanted to knowif anyone cangive me a guide.

1.Ineed to capturea configurationof the operating systemUbuntu.

2.How to assignthe computer namebeingdeploymnet.

3.The ability toperform the joindomain.

Sorry formy English.

thanks
↧
Search

Can I inject drivers into a .wim file on usb boot media?

November 20, 2014, 8:00 am
$
0
0

Hi,

I have been working for days trying to install win7 64 bit on a HP Z620 machine and I keep getting the error “Windows failed to load because of a critical system driver is missing, or corrupt.” 0xc0000359 iastore.sys. I am fairly new to SCCM and I don't want to mess with the productive boot image so I was wondering can I inject the iastore.sys drivers into the boot wim file on a thumb drive? All I have found is examples only using config manager and modifying the productive boot wim. Is this possible? Thank you

↧
↧

WinPE 5 error access denied when applying .wim

November 20, 2014, 12:14 pm
$
0
0

Hello TechNet,

I have been struggling with deploying surface pro 3s using DISM.  I keep receiving an access denied error when I try to apply a windows image to a brand new surface pro 3 using the latest version of DISM.  Any insight would be greatly appreciated.

Regards,

↧

The RPC server is unavailable when PXE booting

November 20, 2014, 11:54 am
$
0
0

Hi,

I am trying to PXE boot a machine that I have been successfully able to do many times this morning but now when I try to login when it asks for credentials I get the message that the "RPC server is unavailable" and I cant continue. Because I have some issues with this machine regarding storage drivers I have been PXE booting this machine all day. Could that be the reason that I have done it too many times with this machine? I have tested with other machines and it works fine no problems. I verified by hitting F8 and I was able to ping the server and I have an IP address so I am really stumped. Seems to be isolated to this machine? TIA


↧

Recent schannel updates caused issues...

November 20, 2014, 12:32 pm
$
0
0

We recently applied updates to our SCCM 2012 server for the SCHANNEL patches MS14-066 updates and the MS14-068 and this caused us a bunch of grief.

As well a hotfix to improve performance also caused us some config manager client installation issues.

Installing the schannel updates resulted in settings changes to the HTTP vs HTTPS in our distribution and also turned off PXE...

Administration>>General

HTTPS changed to HTTP (changing back requires reconfirming the certificate)

Administration>>PXE

Enable PXE support for clients was unchecked.

The other lesson we learned was with a performance hotfix that also required a patch to the client. That patch is apparently not cached to the workstation image it downloads so on Config Manager installation (and patching) the patch had to come from the share on the distribution point and in our case we had not granted Domain Computers read access to that share so the patch was failing. This resulted in machimnes being imaged left in the "in progress" state instead of Success and the Config Manager client install failed to patch and it was old.

Sorry for the vague descriptions... I am NOT our SCCM person, just figured this may help someone ending up in the same place recently.

↧

Failed to Resolve Select Task Sequence Dependcies - Source Version 1

November 20, 2014, 6:08 am
$
0
0

I've been trying to deploy a OSD task sequence via PXE and I've been continually running into an issue where a select application is not found.  Of course, this application has been distributed to all distribution points so that's not the issue.

As soon as I update the application to the DP's, the error goes away for that particular application, but I get another application that cannot be found. One pattern that I've noticed is that all these applications that give me issues are Soure Version 1; so far none of the applications that are Version 2 or greater have given me issues. Anyone know why this might be happening?

↧
↧

no activity on smspxe.log and I am not getting very far when testing OS deployment

November 14, 2014, 12:24 pm
$
0
0

Hello and thanks for any help. I have a few OS deployment issues.

1. There is no activity on smspxe.log. This has been a problem for two weeks. I believe it is a symptom of trying to fix a bigger issue (#2)

2. I am trying to move us from SCE imaging to SCCM 2012. We had CM working at first but had to switch back. Now when I try to do a PXE boot, I see this message.

Recovery
Your PC needs to be repaired
The Windows Boot Configuration Data file from the PXE server does not contain a valid operating system entry. Ensure that the server has boot images installed for this architecture.

File:\Tmp\x86x64{BBD9AF6-E64E-41A9-840504118DB33B45}.bcd
Error code: 0xc0000098

I have tried these steps -  disable PXE on the DP (which is also the MP), remove WDS, I hid the remote install folder, restarted server, installed the WDS role. It wouldn't start so I did wdsutil initialize. Enabled PXE. Maybe important to note; before this the remoteinstall share was RemoteInstall. Now it is "REMINST".

I have boot images for both i386 and x64.

Thanks so much for any help.


↧

PXE Boot one workstation at a time

November 20, 2014, 6:53 am
$
0
0

I have a bit of a problem

here is my setup.

I have a secondary site  and a Distro point at a remote site pointing to the secondary site.

the ping rate is  540ms  from the DP to the secondary site.   Workstations can PXE boot at the remote site, but only one workstation at a time.  If the second PXE boot is started  it will start,  but fail before the option appears to enter the password to chose the task sequence list.

have you seen this happen before?  How can I resolve this?

↧
Search

SCCM 2012: OSD to VHDX, deploy VHDX bare metal via TS?

November 20, 2014, 12:36 am
$
0
0

Hi,

QuestionI wonder what your point of view is on the following scenario:

1.Deploy ts to vhdx
2.Deploy this vhdx to pc  (bare metal) via another ts, this ts would then:
-wipe the disk
-make bootpartition
-add vdisk via bcdboot
It would give a lot of flexibility in terms of deployment speed (only 1 file to deploy, not that many reboots)backup (mount vhd to recover data),adding extra os, running clients vhd on hyperv host ...

Only issue would be how to add machine specific drivers.

Please advise.
J.

Jan Hoedt

↧

UEFI PXE BOOT ERROR

November 14, 2014, 7:06 am
$
0
0

Hi,

I've a problem with the UEFI PXE in SCCM 2012R2.

My DHCP configuration:

Option 66 : myserveripaddress
Option 67 : SMSBoot\x64\wdsmgfw.efi
Option 60 : support

When I try to boot the machine (Hp Pro x2 612) the PXE starts but I receive the error:

Windows Deployment Services encountered an error:
Error Code: 0x102

Any Help is appreciated :)

↧
↧

create MDT sequence

November 20, 2014, 9:20 pm
$
0
0
what is use MDT of packages (package settings etc) hose are created while deploying OS with create MDT sequence
↧

The Epic battle with SMSTSPostAction Continues...help

May 16, 2014, 7:26 am
$
0
0

Can anyone confirm that  SMSTSPostACTION still works with Configmgr 2012 R2? I know it worked with R1 because I used it all the time

Any command I use in SMSTSPostAction is seemly ignored, it's driving me crazy.

↧

MDT OSD Issue - Parse Base Variable failing

November 21, 2014, 7:05 am
$
0
0

We are currently using SCCM 2012 R2 for our Win7 deployments. We have now integrated MDT 2013, mainly to use UDI. Everything is working great except the results screen. The task sequence errors out on the Parse Base Variable command. I've been unable to determine why, but I have found this post:

http://www.myitforum.com/forums/MDT-2012-UDI-OSD-Results-Window-Installed-Applications-Unknown-m235557.aspx

It talks about replacing some of the scripts with those from MDT 2010. I'm just wondering if anyone has run across the same issue and has implemented this particular fix, or has found another solution for this? I just wanted to reach out before opening a case with MS.

Thanks in advance!

↧
Viewing all 9126 articles
Browse latest View live
Search
<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>