Quantcast
Channel: Microsoft Deployment Toolkit forum
Viewing all 11297 articles
Browse latest View live
↧

Looking for 2004 updates for WSUS.

August 25, 2020, 9:20 am
$
0
0

I started looking into setting up a WSUS on a Server2012R2 server. I checked a few things like Office and such,
but I don't see anything higher than updates for 1909.

What must I do to see updates for 2004? The whole purpose of having to set this up is because our Security Group
has blocked us from getting 2004 updates and they don't know the solution to just get them from MS so I have to
set this up.

Is it even possible to pull down 2004 updates on this server? I see when choosing specifics, there is no option for 1809, 1909 or 2004. I also don't see an option for only one architecture over the other, so there's lots of approvals to go through.

My main issue is not seeing any updates for 2004 OS.

I do see an option for Windows 10, 1809 and later, then Win10, 1909 and later, so I guess I don't need 1909 or later as that should be covered by the 1809 option.
Then, there is just one that says Windows 10. I have no idea what I would be pulling down with that.


↧
Search

I'm wondering how Updates work during a Feature Update.

August 25, 2020, 12:01 pm
$
0
0
I tested a few updates in WSUS and they seem to work. However, GPO pushes the OS from 1809 to 1903 during the Pre-Installation for Updates. How would I get 1903 updates? The pc hasn't recognized that it is now 1903. I keep doing a winver during the Deploy and shows 1809.
↧
↧

Looking for a silent switch to work in MDT.

August 12, 2020, 11:23 am
$
0
0

I have an exe that I can run silently on a pc. It does not run in my TS.

I've added lots of exe's before but I can't get this to work.

There is nothing to extract from it, like an MSI.

The file folder has a setup.exe which works on the pc with /s

The error I get is 1603, which I think I found references no access to the file.

This is for a Realtek Audio driver for a Dell 5750 and I took it right off their site.

Does anyone know what solution would get this to silent install in MDT?
I tried /? and /Help and ?dweunreo (garbage) to get a menu but nothing comes up.
Dell and their "full" CAB files. :/

↧

Asking what the difference is in suppression codes.

August 13, 2020, 6:44 am
$
0
0

I have a program installing silently which requires a reboot so it throws an error code 2.

On the Properties tab of the step in my TS, I added a 2 and that's fine.

What is the difference, if any, between adding a code there, or in the Options tab where it asks the same thing?

I see that adding the code on the Properties tab does not update the Options tab, so I'm just curious what the difference is.


↧

WDS Version and MDT /AIK Question

August 27, 2020, 9:56 am
$
0
0

Hi Everyone

So I have a stupid question, but I guess valid nonetheless. So let me paint the picture first.

We have a Production Server 2012 R2 server with WDS and MDT installed. This is currently used to image Windows 10 1809 computers without any issue. 

We then proceeded to build a new MDT Image Development Server with Server 2016 (No WDS, Boot WIM is loaded on the Production WDS server and clients are passed on to the dev MDT server), and the latest MDT, etc.

This all works fine and there are no issues there.

So my question is, would there be a need for me to upgrade the Production server to Server 2016?

So my thoughts around this are. I do not think there would be any major difference, as long as the MDT, WAIK, etc on the Production server is upgraded to the latest version, the WDS version should not matter in this case.

The understanding is the client will perform a PXE boot, the PROD WDS server will provide them a list of BOOT images, this will load the client into the WinPE environment and perform a LiteTouch Install. This all connects to my MDT deployment share (which will now be hosted on the Production Server) and it really just takes the files off that and completes the installation.

Regards

Louwrens

Kind Regards Louwrens

↧
↧

Why do all Junction Points point to D:\ and not C:\ after deployment?

September 10, 2019, 10:07 am
$
0
0

Running MDT 8456, ADK 1903, and Windows PE Add-on 1903

Deploying Windows 10 LTSC 2019

After deploying the image all Junction Points still exist, however, they are begin with D:\

What cause this and how do I fix it?

↧

What's the best way to set IE home page now?

September 3, 2020, 5:27 am
$
0
0

I was setting our Home Page in my unattend files and they worked great.

Now I just get "about" in the URL. I know you can set it in the CS.INI but I don't know the syntax. I tried what I saw once
on a forum post in here but it didn't apply.

Any help would be appreciated. (Win10 x64 2004).

↧

Updated ADK and winPE for windows version 2004 and now the image isn't working.

September 4, 2020, 10:37 am
$
0
0

i updated the adk, winpe and language packs for windows version 2004. after the image applies it immediately goes to this error screen:

here  are the log files: https://www.dropbox.com/sh/g3wja79g0munuv2/AAAQ4S7lkm6y963Z_FjH2Gtsa?dl=0

i have poured over these and have not been able to resolve the error. any help would be great. 

thank you! 

↧
Search

I have some confusion about configuring Windows Updates.

September 4, 2020, 11:34 am
$
0
0

In my Deploy TS, I have a registry set to Stop Driver Updates.

If I let MDT finish and manually run updates, I get a few .NET updates and maybe a cumulative update.

When I enable Updates to run through MDT, (with Stop Driver Updates higher up in my TS), I get all kinds of driver updates.

We don't want any driver updates of any kind when we Check For Updates (and we don't). So, I'm wondering why I get them
during MDT running the updates for me.

Any idea how to stop those? It would be good to have MDT run Windows Updates during imaging.


↧
↧

Dism Host Servicing Process has stopped working

April 6, 2016, 4:42 pm
$
0
0

I provisioned a new Windows 2012 server for creating reference image using MDT.

However, when I update the deployment share, an error occurs "Dism Host Servicing Process has stopped working"

ADK 10
MDT 2013 Update 2
Windows 2012 R2
built on VMware

↧

MDT Error - Cannot deploy image

July 1, 2019, 1:31 am
$
0
0

Hello, MDT Experts

May I ask your help on how to fix this MDT error after completing ScanState part. I am going to upgrade Windows 10 enterprise client to Windows 10 LTSB by deploying a complete Windows 10 image.

Expectation is that it should restart and apply Windows 10 image after backing up user data and settings.

By the way, this is an isolated case, other deployments are okay.

Error:

ZTI ERROR - Unhandled error returned by LTIApply: Invalid procedure call or argument

Below is a part of BDD logs.

TargetOS is the current SystemDrive LTIApply 6/19/2019 6:26:35 PM 0 (0x0000)
Get the Boot Drive. LTIApply 6/19/2019 6:26:35 PM 0 (0x0000)
The current autorun setting is - 145 LTIApply 6/19/2019 6:26:35 PM 0 (0x0000)
Disabling Autorun LTIApply 6/19/2019 6:26:35 PM 0 (0x0000)
Find the boot drive (if any) [True] [10.0.14393.2999] [False] LTIApply 6/19/2019 6:26:35 PM 0 (0x0000)
New ZTIDisk : \\Client\root\cimv2:Win32_DiskDrive.DeviceID="\\\\.\\PHYSICALDRIVE0" LTIApply 6/19/2019 6:26:35 PM 0 (0x0000)
DISKPART + Select Disk 0 LTIApply 6/19/2019 6:26:35 PM 0 (0x0000)
DISKPART + Select Partition 1 LTIApply 6/19/2019 6:26:35 PM 0 (0x0000)
DISKPART + Assign LTIApply 6/19/2019 6:26:35 PM 0 (0x0000)
DISKPART + Exit LTIApply 6/19/2019 6:26:35 PM 0 (0x0000)
About to run command: cscript.exe //nologo "\\​Server\MDTShare$\Scripts\ztiRunCommandHidden.wsf" "DiskPart.exe /s C:\Users\MADORA~1\AppData\Local\Temp\rad1A944.tmp" LTIApply 6/19/2019 6:26:36 PM 0 (0x0000)
About to run command: DiskPart.exe /s C:\Users\MADORA~1\AppData\Local\Temp\rad1A944.tmp ztiRunCommandHidden 6/19/2019 6:26:37 PM 0 (0x0000)
Command has been started (process ID 8476) ztiRunCommandHidden 6/19/2019 6:26:37 PM 0 (0x0000)
ZTI Heartbeat: command has been running for 0 minutes (process ID 8476) ztiRunCommandHidden 6/19/2019 6:26:37 PM 0 (0x0000)
  Console > Microsoft DiskPart version 6.1.7601 ztiRunCommandHidden 6/19/2019 6:26:37 PM 0 (0x0000)
  Console > Copyright (C) 1999-2008 Microsoft Corporation. ztiRunCommandHidden 6/19/2019 6:26:37 PM 0 (0x0000)
  Console > On computer: DRICH7-TP ztiRunCommandHidden 6/19/2019 6:26:37 PM 0 (0x0000)
  Console > Disk 0 is now the selected disk. ztiRunCommandHidden 6/19/2019 6:26:50 PM 0 (0x0000)
  Console > Partition 1 is now the selected partition. ztiRunCommandHidden 6/19/2019 6:26:50 PM 0 (0x0000)
  Console > There is no volume specified. ztiRunCommandHidden 6/19/2019 6:26:55 PM 0 (0x0000)
  Console > Please select a volume and try again. ztiRunCommandHidden 6/19/2019 6:26:55 PM 0 (0x0000)
Return code from command = -2147024809 ztiRunCommandHidden 6/19/2019 6:26:55 PM 0 (0x0000)
Command has returned: -2147024809 LTIApply 6/19/2019 6:26:55 PM 0 (0x0000)
No boot drives found. None. LTIApply 6/19/2019 6:28:00 PM 0 (0x0000)
Reverting autorun setting to - 145 LTIApply 6/19/2019 6:28:00 PM 0 (00000)
Boot Drive not found, attempting recovery option (Win8+Sysprep scenario)... LTIApply 6/19/2019 6:28:00 PM 0 (0x0000)
Found Recovery option: MBR 0 1 1 17 304    304 LTIApply 6/19/2019 6:28:02 PM 0 (0x0000)
ZTI ERROR - Unhandled error returned by LTIApply: Invalid procedure call or argument (5) LTIApply 6/19/2019 6:28:02 PM 0 (0x0000)

Any help on this will be much appreciated. Thank you in advance.

Cheers,

Michael

↧

How to get rid of Windows Deployment Wizard after installation has been completed

September 8, 2020, 5:10 am
$
0
0

Hi Guys,

I'm trying now few good weeks to get rid of this Windows Deployment Wizard at the end of deployment process. Every time I have to click Next Next Next on this wizard to finish up my deployment. It is very annoing especialy when you want to do fully unattended deployment. Im using Win 2019 Latest ADK and MDT aprox they are 3 months old. SkipSummary and SkipFinalSummary are set to YES. 

These are my Settings:

[Settings]
Priority=Default
Properties=MyCustomProperty

[Default]
DeployRoot=\\172.18.22.165\MDT$
UserDomain=infy.com
SkipBDDWelcome=YES
OSInstall=YES
Adminpassword=123456
SkipCapture=YES
SkipAdminPassword=YES
SkipProductKey=YES
SkipComputerBackup=YES
SkipBitLocker=YES
SkipUserData=YES
SkipDomainMembership=NO
SkipLocaleSelection=YES
HideShell=No
UserDataLocation=NONE
TimeZone=100
TimeZoneName=Central European Standard Time
SkipTimeZone=YES
SkipLocaleSelection=YES
UILanguage=en-us
UserLocale=pl-PL
KeyboardLocale=0415:00000415
OSDComputerName=BPMLCJ
SkipSummary=YES
SkipFinalSummary=YES
TaskSequenceID=1909_HARDEN
SLSHARE=\\172.18.22.165\logs$


↧

Wizard.hta blank - The system cannot locate the object specified Control\\TS.XML

December 4, 2019, 4:04 am
$
0
0

Dear TechNet,

last time my MDT server stoped to work properly. When I boot from PXE and get wizard.hta blank.

When I capture logs I get:

<![LOG[Reading \\mdt\DeploymentShare$\Control\\TS.XML]LOG]!><time="11:10:31.000+000" date="12-04-2019" component="LiteTouch" context="" type="1" thread="" file="LiteTouch"><![LOG[File: \\mdt\DeploymentShare$\Control\\TS.XML Line: 0 - The system cannot locate the object specified.
 - ]LOG]!><time="11:10:31.000+000" date="12-04-2019" component="LiteTouch" context="" type="2" thread="" file="LiteTouch"><![LOG[FAILURE ( 5495 ): -2146697210  0x800C0006: Create MSXML2.DOMDocument  .ParseErr.ErrCode.]LOG]!><time="11:10:31.000+000" date="12-04-2019" component="LiteTouch" context="" type="3" thread="" file="LiteTouch"><![LOG[Event 41002 sent: FAILURE ( 5495 ): -2146697210  0x800C0006: Create MSXML2.DOMDocument  .ParseErr.ErrCode.]LOG]!><time="11:10:33.000+000" date="12-04-2019" component="LiteTouch" context="" type="1" thread="" file="LiteTouch">

It's strange - I have nothing changed in MDT configuration. Only one thing could happen - Windows Update but there is no info about any KB that breaks MDT... I have Winows Server 2016 x64 1607 and MDT 6.3.8456

In log i see Control\\TS.XML -looks like path to Task Sequence is not valid. It happens before wizzard with options to choose proper task sequence shows up.



↧
↧

wds/mdt deploying images slow

September 8, 2020, 7:40 am
$
0
0

Hello

I used a Windows Server 2019 with wds and mdt, it can deploy os.

Both the server and the client are 1G networks, But there are usually only 100M to 200M when deploying images, 

The CPU usage is not high and CPU is i5-6500 @3.5ghz, The image is about 12GB

How can I speed it up?

↧

MDT 2013 Powershell script not working on deployment

September 8, 2020, 9:25 am
$
0
0

Hello,

I am currently working on setting up an MDT 2013 deployment in order to distribute Windows 10 as an image to multiple devices throughout the business I'm working in.

I have configured MDT to deploy an image with certain programs successfully pre-installed on it, these programs are:

  • Adobe Reader DC

  • Google Chrome

  • .Net framework 2.0-3.5.1

  • Office 365 Apps for enterprise

I'm currently trying to get it to install an older application which does not have a .MSI for me to use, only a .exe file. To get around this, I have created a powershell script which, among other functions, copies the files required for the installation across and performs a silent install in the background. This has been tested on computers joined to the domain and computers not joined to the domain, however when I attempt to add the script as an application in MDT, it fails every time with a rather generic error which doesn't seem to tell me very much.

After looking into this quite extensively I determined it might be the Execution policy causing a problem, however after injecting a registry key to set the policy to unrestricted I now receive a different error code, the error code is "Appliaction AppName returned an unexpected return code: 1" I cannot seem to find any further information about this, can anyone suggest anything for me to look at please?

Many thanks,

Chris Stendall
↧
Search

Diskpart set id command not working

January 4, 2013, 9:05 pm
$
0
0

I am attempting to use "set id=84 override" to recreate a hidden hibernation partition. I select the disk, then partition then type set id=84 override but then I get a message stating "The specified type is not in the correct format."

Per the Intel Rapid Start documentation this is the correct command. What can I do to correct this.

↧

DISM\unattend.xml error

September 9, 2020, 9:37 am
$
0
0

I am getting the following error when running a task sequence in a VM (you'll have to remote the space after the last backslash, I'm not allowed to post images or links yet): 

https://imgur.com/ EAdPRiM

It happens after installing the OS when DISM tries to apply unattend.xml. The task sequence does nothing but install 2004. No drivers, no applications, just as simple as I could make it.

Back in the deployment share, when I import the 2004 operating system I use the full set of source files and get them from E:, which is just a mounted image of 2004 Enterprise on the MDT server. In the task sequence I select the install.wim of 2004 Enterprise that was created during the import.

In the unattend.xml file for this task sequence, components\windowsPE\amd64_*\ImageInstall\OSImage\InstallFrom correctly uses .\Operating Systems\Windows102004\Sources\install.wim

I'm not sure if the deployment doesn't get far enough, but in the deployment share no log files are ever made. Within the VM, once the deployment fails, it opens up a command prompt which I direct to X:\MININT\SMSOSD\OSDLOGS\BDD.log. Within the log file there are no errors, it seems to format the E: drive (not sure if this is the wrong drive) and then ends, but shows no error.

Looking through the forums I've found people with the same error, but none of the solutions seem to work for me. Does anyone know why this might be happening? If you need any additional info please let me know.

↧
↧

DISM 112 Error when capturing image

September 10, 2020, 10:20 am
$
0
0

I am getting a DISM 112 error when trying to capture an image.  I have been using the same process for several years but this time I am getting an error saying the disk is full.  I have tried capturing the image to several different locations with the same result.  

Any help would be greatly appreciated.

Here's what the log file says.

2020-09-10 11:15:13, Info                  DISM   PID=812 TID=712 Scratch directory set to 'X:\windows\TEMP\'. - CDISMManager::put_ScratchDir
2020-09-10 11:15:13, Info                  DISM   PID=812 TID=712 DismCore.dll version: 6.2.9200.16384 - CDISMManager::FinalConstruct
2020-09-10 11:15:13, Info                  DISM   PID=812 TID=712 Successfully loaded the ImageSession at "X:\windows\System32\Dism" - CDISMManager::LoadLocalImageSession
2020-09-10 11:15:13, Info                  DISM   DISM Provider Store: PID=812 TID=712 Found and Initialized the DISM Logger. - CDISMProviderStore::Internal_InitializeLogger
2020-09-10 11:15:13, Info                  DISM   DISM Provider Store: PID=812 TID=712 Failed to get and initialize the PE Provider.  Continuing by assuming that it is not a WinPE image. - CDISMProviderStore::Final_OnConnect
2020-09-10 11:15:13, Info                  DISM   DISM Provider Store: PID=812 TID=712 Finished initializing the Provider Map. - CDISMProviderStore::Final_OnConnect
2020-09-10 11:15:13, Info                  DISM   DISM Provider Store: PID=812 TID=712 Getting Provider DISMLogger - CDISMProviderStore::GetProvider
2020-09-10 11:15:13, Info                  DISM   DISM Provider Store: PID=812 TID=712 Provider has previously been initialized.  Returning the existing instance. - CDISMProviderStore::Internal_GetProvider
2020-09-10 11:15:13, Info                  DISM   DISM Provider Store: PID=812 TID=712 Getting Provider DISMLogger - CDISMProviderStore::GetProvider
2020-09-10 11:15:13, Info                  DISM   DISM Provider Store: PID=812 TID=712 Provider has previously been initialized.  Returning the existing instance. - CDISMProviderStore::Internal_GetProvider
2020-09-10 11:15:13, Info                  DISM   DISM Manager: PID=812 TID=712 Successfully created the local image session and provider store. - CDISMManager::CreateLocalImageSession
2020-09-10 11:15:13, Info                  DISM   DISM Provider Store: PID=812 TID=712 Getting Provider DISMLogger - CDISMProviderStore::GetProvider
2020-09-10 11:15:13, Info                  DISM   DISM Provider Store: PID=812 TID=712 Provider has previously been initialized.  Returning the existing instance. - CDISMProviderStore::Internal_GetProvider
2020-09-10 11:15:13, Info                  DISM   DISM.EXE: 
2020-09-10 11:15:13, Info                  DISM   DISM.EXE: <----- Starting Dism.exe session ----->
2020-09-10 11:15:13, Info                  DISM   DISM.EXE: 
2020-09-10 11:15:13, Info                  DISM   DISM.EXE: Host machine information: OS Version=6.2.9200, Running architecture=amd64, Number of processors=4
2020-09-10 11:15:13, Info                  DISM   DISM.EXE: Dism.exe version: 6.2.9200.16384
2020-09-10 11:15:13, Info                  DISM   DISM.EXE: Executing command line: dism  /capture-image /imagefile:N:\win10entx64cadd-9-10-20.wim /capturedir:O:\ /name:"Windows 10 Enterprise x64 CADD Image"
2020-09-10 11:15:13, Info                  DISM   DISM Provider Store: PID=812 TID=712 Getting the collection of providers from a local provider store type. - CDISMProviderStore::GetProviderCollection
2020-09-10 11:15:13, Info                  DISM   DISM Provider Store: PID=812 TID=712 Provider has not previously been encountered.  Attempting to initialize the provider. - CDISMProviderStore::Internal_GetProvider
2020-09-10 11:15:13, Info                  DISM   DISM Provider Store: PID=812 TID=712 Loading Provider from location X:\windows\System32\Dism\FolderProvider.dll - CDISMProviderStore::Internal_GetProvider
2020-09-10 11:15:13, Info                  DISM   DISM Provider Store: PID=812 TID=712 Connecting to the provider located at X:\windows\System32\Dism\FolderProvider.dll. - CDISMProviderStore::Internal_LoadProvider
2020-09-10 11:15:13, Info                  DISM   DISM Provider Store: PID=812 TID=712 Provider has not previously been encountered.  Attempting to initialize the provider. - CDISMProviderStore::Internal_GetProvider
2020-09-10 11:15:13, Info                  DISM   DISM Provider Store: PID=812 TID=712 Loading Provider from location X:\windows\System32\Dism\WimProvider.dll - CDISMProviderStore::Internal_GetProvider
2020-09-10 11:15:13, Info                  DISM   DISM Provider Store: PID=812 TID=712 Connecting to the provider located at X:\windows\System32\Dism\WimProvider.dll. - CDISMProviderStore::Internal_LoadProvider
2020-09-10 11:15:13, Info                  DISM   DISM Provider Store: PID=812 TID=712 Provider has not previously been encountered.  Attempting to initialize the provider. - CDISMProviderStore::Internal_GetProvider
2020-09-10 11:15:13, Info                  DISM   DISM Provider Store: PID=812 TID=712 Loading Provider from location X:\windows\System32\Dism\VHDProvider.dll - CDISMProviderStore::Internal_GetProvider
2020-09-10 11:15:13, Info                  DISM   DISM Provider Store: PID=812 TID=712 Connecting to the provider located at X:\windows\System32\Dism\VHDProvider.dll. - CDISMProviderStore::Internal_LoadProvider
2020-09-10 11:15:13, Info                  DISM   DISM Provider Store: PID=812 TID=712 Provider has not previously been encountered.  Attempting to initialize the provider. - CDISMProviderStore::Internal_GetProvider
2020-09-10 11:15:13, Info                  DISM   DISM Provider Store: PID=812 TID=712 Loading Provider from location X:\windows\System32\Dism\ImagingProvider.dll - CDISMProviderStore::Internal_GetProvider
2020-09-10 11:15:13, Info                  DISM   DISM Provider Store: PID=812 TID=712 Connecting to the provider located at X:\windows\System32\Dism\ImagingProvider.dll. - CDISMProviderStore::Internal_LoadProvider
2020-09-10 11:15:13, Info                  DISM   DISM Provider Store: PID=812 TID=712 Provider has not previously been encountered.  Attempting to initialize the provider. - CDISMProviderStore::Internal_GetProvider
2020-09-10 11:15:13, Info                  DISM   DISM Provider Store: PID=812 TID=712 Loading Provider from location X:\windows\System32\Dism\CompatProvider.dll - CDISMProviderStore::Internal_GetProvider
2020-09-10 11:15:13, Info                  DISM   DISM Provider Store: PID=812 TID=712 Connecting to the provider located at X:\windows\System32\Dism\CompatProvider.dll. - CDISMProviderStore::Internal_LoadProvider
2020-09-10 11:15:13, Info                  DISM   DISM.EXE: Got the collection of providers. Now enumerating them to build the command table.
2020-09-10 11:15:13, Info                  DISM   DISM.EXE: Attempting to add the commands from provider: DISM Log Provider
2020-09-10 11:15:13, Info                  DISM   DISM.EXE: Attempting to add the commands from provider: FolderManager
2020-09-10 11:15:13, Info                  DISM   DISM.EXE: Attempting to add the commands from provider: WimManager
2020-09-10 11:15:13, Info                  DISM   DISM.EXE: Succesfully registered commands for the provider: WimManager.
2020-09-10 11:15:13, Info                  DISM   DISM.EXE: Attempting to add the commands from provider: VHDManager
2020-09-10 11:15:13, Info                  DISM   DISM.EXE: Attempting to add the commands from provider: GenericImagingManager
2020-09-10 11:15:13, Info                  DISM   DISM.EXE: Succesfully registered commands for the provider: GenericImagingManager.
2020-09-10 11:15:13, Info                  DISM   DISM.EXE: Attempting to add the commands from provider: Compatibility Manager
2020-09-10 11:15:13, Info                  DISM   DISM.EXE: Succesfully registered commands for the provider: Compatibility Manager.
2020-09-10 11:15:13, Info                  DISM   DISM Provider Store: PID=812 TID=712 Getting Provider WimManager - CDISMProviderStore::GetProvider
2020-09-10 11:15:13, Info                  DISM   DISM Provider Store: PID=812 TID=712 Provider has previously been initialized.  Returning the existing instance. - CDISMProviderStore::Internal_GetProvider
[812] [0xc144012f] 
2020-09-10 11:15:14, Info                  DISM   DISM WIM Provider: PID=812 O:\Program Files\Bentley\DgnODBCDriver\ODBCCfg.dll (HRESULT=0x8007011A) - CWimManager::WimProviderMsgLogCallback
[812] [0xc144012f] 
2020-09-10 11:15:14, Info                  DISM   DISM WIM Provider: PID=812 O:\Program Files\Bentley\DgnODBCDriver\simbaicudt38_64.dll (HRESULT=0x8007011A) - CWimManager::WimProviderMsgLogCallback
[812] [0xc144012f] 
2020-09-10 11:15:14, Info                  DISM   DISM WIM Provider: PID=812 O:\Program Files\Bentley\DgnODBCDriver\simbaicuuc38_64.dll (HRESULT=0x8007011A) - CWimManager::WimProviderMsgLogCallback
[812] [0xc144012f] 
2020-09-10 11:15:15, Info                  DISM   DISM WIM Provider: PID=812 O:\Program Files\Common Files\Bentley Shared\CONNECTION client\Bentley.Connect.Client.API.dll (HRESULT=0x8007011A) - CWimManager::WimProviderMsgLogCallback
[812] [0xc144012f] 
2020-09-10 11:15:15, Info                  DISM   DISM WIM Provider: PID=812 O:\Program Files\Common Files\Bentley Shared\CONNECTION client\Bentley.Connect.Client.BeLogger.dll (HRESULT=0x8007011A) - CWimManager::WimProviderMsgLogCallback
[812] [0xc144012f] 
2020-09-10 11:15:15, Info                  DISM   DISM WIM Provider: PID=812 O:\Program Files\Common Files\Bentley Shared\CONNECTION client\Bentley.Connect.Client.CloudLib.dll (HRESULT=0x8007011A) - CWimManager::WimProviderMsgLogCallback
[812] [0xc144012f] 
2020-09-10 11:15:15, Info                  DISM   DISM WIM Provider: PID=812 O:\Program Files\Common Files\Bentley Shared\CONNECTION client\Bentley.Connect.Client.Common.dll (HRESULT=0x8007011A) - CWimManager::WimProviderMsgLogCallback
[812] [0xc144012f] 
2020-09-10 11:15:15, Info                  DISM   DISM WIM Provider: PID=812 O:\Program Files\Common Files\Bentley Shared\CONNECTION client\Bentley.Connect.Client.exe (HRESULT=0x8007011A) - CWimManager::WimProviderMsgLogCallback
[812] [0xc144012f] 
2020-09-10 11:15:15, Info                  DISM   DISM WIM Provider: PID=812 O:\Program Files\Common Files\Bentley Shared\CONNECTION client\Bentley.Connect.Client.Extensibility.dll (HRESULT=0x8007011A) - CWimManager::WimProviderMsgLogCallback
[812] [0xc144012f] 
2020-09-10 11:15:15, Info                  DISM   DISM WIM Provider: PID=812 O:\Program Files\Common Files\Bentley Shared\CONNECTION client\Bentley.Connect.Client.Framework.dll (HRESULT=0x8007011A) - CWimManager::WimProviderMsgLogCallback
[812] [0xc144012f] 
2020-09-10 11:15:15, Info                  DISM   DISM WIM Provider: PID=812 O:\Program Files\Common Files\Bentley Shared\CONNECTION client\Bentley.Connect.Client.PrefSyncAPI.dll (HRESULT=0x8007011A) - CWimManager::WimProviderMsgLogCallback
[812] [0xc144012f] 
2020-09-10 11:15:15, Info                  DISM   DISM WIM Provider: PID=812 O:\Program Files\Common Files\Bentley Shared\CONNECTION client\Bentley.Connect.Client.Service.Interface.dll (HRESULT=0x8007011A) - CWimManager::WimProviderMsgLogCallback
[812] [0xc144012f] 
2020-09-10 11:15:15, Info                  DISM   DISM WIM Provider: PID=812 O:\Program Files\Common Files\Bentley Shared\CONNECTION client\Bentley.Connect.Client.Service.Server.dll (HRESULT=0x8007011A) - CWimManager::WimProviderMsgLogCallback
[812] [0xc144012f] 
2020-09-10 11:15:15, Info                  DISM   DISM WIM Provider: PID=812 O:\Program Files\Common Files\Bentley Shared\CONNECTION client\Bentley.Connect.Client.UITools.dll (HRESULT=0x8007011A) - CWimManager::WimProviderMsgLogCallback
[812] [0xc144012f] 
2020-09-10 11:15:15, Info                  DISM   DISM WIM Provider: PID=812 O:\Program Files\Common Files\Bentley Shared\CONNECTION client\Bentley.License.Library.10.NET.dll (HRESULT=0x8007011A) - CWimManager::WimProviderMsgLogCallback
[812] [0xc144012f] 
2020-09-10 11:15:15, Info                  DISM   DISM WIM Provider: PID=812 O:\Program Files\Common Files\Bentley Shared\CONNECTION client\Bentley.liclib.10.dll (HRESULT=0x8007011A) - CWimManager::WimProviderMsgLogCallback
[812] [0xc144012f] 
2020-09-10 11:15:15, Info                  DISM   DISM WIM Provider: PID=812 O:\Program Files\Common Files\Bentley Shared\CONNECTION client\Bentley.lictransmit.exe (HRESULT=0x8007011A) - CWimManager::WimProviderMsgLogCallback
[812] [0xc144012f] 
2020-09-10 11:15:15, Info                  DISM   DISM WIM Provider: PID=812 O:\Program Files\Common Files\Bentley Shared\CONNECTION client\Bentley.logging-2.0.dll (HRESULT=0x8007011A) - CWimManager::WimProviderMsgLogCallback
[812] [0xc144012f] 
2020-09-10 11:15:15, Info                  DISM   DISM WIM Provider: PID=812 O:\Program Files\Common Files\Bentley Shared\CONNECTION client\Bentley.Logging.log4net-2.0.dll (HRESULT=0x8007011A) - CWimManager::WimProviderMsgLogCallback
[812] [0xc144012f] 
2020-09-10 11:15:15, Info                  DISM   DISM WIM Provider: PID=812 O:\Program Files\Common Files\Bentley Shared\CONNECTION client\Bentley.Select.Shareable.dll (HRESULT=0x8007011A) - CWimManager::WimProviderMsgLogCallback
[812] [0xc144012f] 
2020-09-10 11:15:15, Info                  DISM   DISM WIM Provider: PID=812 O:\Program Files\Common Files\Bentley Shared\CONNECTION client\Bentley.Update.Client.dll (HRESULT=0x8007011A) - CWimManager::WimProviderMsgLogCallback
[812] [0xc144012f] 
2020-09-10 11:15:15, Info                  DISM   DISM WIM Provider: PID=812 O:\Program Files\Common Files\Bentley Shared\CONNECTION client\Bentley.Update.Data.dll (HRESULT=0x8007011A) - CWimManager::WimProviderMsgLogCallback
[812] [0xc144012f] 
2020-09-10 11:15:15, Info                  DISM   DISM WIM Provider: PID=812 O:\Program Files\Common Files\Bentley Shared\CONNECTION client\ConnectClientWrapperNative.VC80.dll (HRESULT=0x8007011A) - CWimManager::WimProviderMsgLogCallback
[812] [0xc144012f] 
2020-09-10 11:15:15, Info                  DISM   DISM WIM Provider: PID=812 O:\Program Files\Common Files\Bentley Shared\CONNECTION client\SQLite.Interop.dll (HRESULT=0x8007011A) - CWimManager::WimProviderMsgLogCallback
[812] [0xc144012f] 
2020-09-10 11:15:15, Info                  DISM   DISM WIM Provider: PID=812 O:\Program Files\Common Files\Diskeeper Corporation\MJS\MJSCR.dll (HRESULT=0x8007011A) - CWimManager::WimProviderMsgLogCallback
[812] [0xc144012f] 
2020-09-10 11:15:15, Info                  DISM   DISM WIM Provider: PID=812 O:\Program Files\Common Files\microsoft shared\ink\InkDiv.dll (HRESULT=0x8007011A) - CWimManager::WimProviderMsgLogCallback
[812] [0xc144012f] 
2020-09-10 11:15:15, Info                  DISM   DISM WIM Provider: PID=812 O:\Program Files\Common Files\microsoft shared\ink\InkObj.dll (HRESULT=0x8007011A) - CWimManager::WimProviderMsgLogCallback
[812] [0xc144012f] 
2020-09-10 11:15:15, Info                  DISM   DISM WIM Provider: PID=812 O:\Program Files\Common Files\microsoft shared\ink\InputPersonalization.exe (HRESULT=0x8007011A) - CWimManager::WimProviderMsgLogCallback
[812] [0xc144012f] 
2020-09-10 11:15:15, Info                  DISM   DISM WIM Provider: PID=812 O:\Program Files\Common Files\microsoft shared\ink\IpsMigrationPlugin.dll (HRESULT=0x8007011A) - CWimManager::WimProviderMsgLogCallback
[812] [0xc144012f] 
2020-09-10 11:15:15, Info                  DISM   DISM WIM Provider: PID=812 O:\Program Files\Common Files\microsoft shared\ink\IpsPlugin.dll (HRESULT=0x8007011A) - CWimManager::WimProviderMsgLogCallback
[812] [0xc144012f] 
2020-09-10 11:15:15, Info                  DISM   DISM WIM Provider: PID=812 O:\Program Files\Common Files\microsoft shared\ink\micaut.dll (HRESULT=0x8007011A) - CWimManager::WimProviderMsgLogCallback
[812] [0xc144012f] 
2020-09-10 11:15:15, Info                  DISM   DISM WIM Provider: PID=812 O:\Program Files\Common Files\microsoft shared\ink\Microsoft.Ink.dll (HRESULT=0x8007011A) - CWimManager::WimProviderMsgLogCallback
[812] [0xc144012f] 
2020-09-10 11:15:15, Info                  DISM   DISM WIM Provider: PID=812 O:\Program Files\Common Files\microsoft shared\ink\mip.exe (HRESULT=0x8007011A) - CWimManager::WimProviderMsgLogCallback
[812] [0xc144012f] 
2020-09-10 11:15:15, Info                  DISM   DISM WIM Provider: PID=812 O:\Program Files\Common Files\microsoft shared\ink\mraut.dll (HRESULT=0x8007011A) - CWimManager::WimProviderMsgLogCallback
[812] [0xc144012f] 
2020-09-10 11:15:15, Info                  DISM   DISM WIM Provider: PID=812 O:\Program File

↧

File copy failing in MDT Task sequence

September 11, 2020, 7:38 am
$
0
0

This is probably a really, really simple problem to fix, but I've been Googling like mad and I cannot find a solution that works for me.

I have set up a working MDT deployment server which is now deploying a Windows 10 image to client machines as it should do. I want to add a simple copy command into the task sequence to copy a folder from my %ScriptRoot% to the C:\ drive of the device being imaged.

I have tried the following commands in TS:

New command line sequence in Custom Tasks with the command: robocopy.exe "%ScriptRoot%\FolderName" "C:\FolderName" /E

The copy fails with the following error:

Incorrect function. (Error: 00000001; Source: Windows)

Does anyone have any ideas why I'm getting this? I'm running this command as-is and not under a specified account, so it's using the default account on the target computer the same as the rest of the task sequence.

Thanks in advance!

↧

New users in 2004 do not get mapped drives at logon.

August 20, 2020, 9:29 am
$
0
0

In my lab, we are admins so most things work for us. But when a new user signs onto a 2004 pc, they do not get
their mapped drives, which GPO pushes at logon. This has worked in 1809 and we are testing out issues in 2004.

We have new users (and non-admin users) who do not get their needed mapped drives that they should at logon.

Is anyone aware of a fix for mapped drives not appearing? Some sites say to disable password protected file sharing, but that
isn't even an option in 2004. SMB1 is enabled by the way.

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