any help
On Tue, Mar 7, 2017 at 11:08 AM, Kevin Ray wrote:
> Hi All,
>
> I have captured my windows10 image(.wim file) with MDT includes custum all
> required applications.
>
> I would like to do further more enhancement while depploying in SCCM with
> adding Custumized
Hi Kevin,
Are you looking to write keys into the Registry to track things like when the
machine was built, the task sequence name and ID?
Something like this:
[cid:image002.png@01D29812.79D6CFC0]
From: listsad...@lists.myitforum.com [mailto:listsad...@lists.myitforum.com] On
Behalf Of
Okay, that’s easy to do.
First, of course you need to decide what specific information you want to store
in the Registry and where you want to store it. I would store it under
HKLM\System so you don’t have to deal with Registry redirection between 32bit
and 64bit builds.
Second, once you
This will do it for you:
http://home.configmgrftw.com/configmgr-osd-information-script/.
J
From: listsad...@lists.myitforum.com [mailto:listsad...@lists.myitforum.com] On
Behalf Of Marable, Mike
Sent: Wednesday, March 8, 2017 1:34 PM
To: mssms
Subject: RE: [mssms]
Yes Mike
On Wed, Mar 8, 2017 at 1:56 PM, Marable, Mike
wrote:
> Hi Kevin,
>
>
>
> Are you looking to write keys into the Registry to track things like when
> the machine was built, the task sequence name and ID?
>
>
>
> Something like this:
>
>
>
>
>
>
>
>
>
> *From:*
Hi,
I have a custom executable to deploy with ConfigMgr that must be run from UNC
path and opens a command prompt while running then closes.
This fails using a task sequence or program.
Manually, the executable fails from command prompt but runs properly from the
Windows Run box.
Any
cmd / c %~dp0.exe
1E | Software Lifecycle Automation
On Mar 8, 2017, at 3:10 PM, Timothy Ransom
> wrote:
Hi,
I have a custom executable to deploy with ConfigMgr that must be run from UNC
path and opens a command prompt while
7 matches
Mail list logo