OK, let me back up a second and see if we can clarify a few things. Are the
following correct?
1. Are you using ConfigMgr to do a build and capture of an OS image?
2. Is your build and capture is performing a domain join during the image
process?
3. Each time you are runnin
Shouldn't leaving it blank default to the Computers container? I just think
you can't point it to Computers directly.
From: listsad...@lists.myitforum.com [mailto:listsad...@lists.myitforum.com]
On Behalf Of Johns, Damon (DoJ)
Sent: Thursday, April 10, 2014 9:41 AM
To: 'mssms@lists.myitforum
I do have a network access account. Its not locked out. Its joining build and
capture images to the domain with the names that were on the computer
previously.
Its just this capture media task image that's causing me grief. I am assuming
that the not joining to the domain had to do with the o
Have you specified an OU in your task sequence under the Apply Network Settings
step? This can't be blank otherwise the domain join will fail, also can't be
set to the Computers container.
Have you specified a network account / verified it's not locked out and that a
network account has been sp
I am re-imaging existing machines. New ones will have the OSDComputername
variable to allow them to enter the name when they deploy.
From: listsad...@lists.myitforum.com [mailto:listsad...@lists.myitforum.com] On
Behalf Of Schwan, Phil
Sent: Wednesday, April 9, 2014 4:20 PM
To: mssms@lists.myit
Sysprep should indeed do that. I would check the setuperr.log and netsetup.log
files on the machine to see what errors are being generated during the process.
As far as the names going forward, is there a particular naming convention you
are looking to implement? There are several options to a
I have an osdcomputername on the unknown collection, but if I am going to be
pushing this out to a group of computers, I want to automate it and not have to
touch each computer to set the name.
I thought sysprep was going to get rid of the name on the capture.
From: listsad...@lists.myitforum.c
How are you setting the computer name during deployment?
-Phil
_
Phil Schwan | Technical Architect, Enterprise Windows Services
Project Leadership Associates | 2000 Town Center, Suite 1900, Southfield, MI
48075
Lync: 312.756.1626 Mo
I created an OSD capture image using the capture media task sequence.
Reference computer was joined to workgroup with blank admin password. However,
when I deploy it, it comes down with the name it originally had and does not
join the domain. I looked up several articles and can't see what I
No, that would get passed round like wild fire :)
Never heard of a reg key to do that
Think I spent 30 mins with this, and it wasn't jumping out as intuitive; I'm
one script away for nailing it I'll go with what I have.
From: listsad...@lists.myitforum.com [mailto:listsad...@lists.myitfo
You need to run that installer on a Remote Desktop Services server. If you are
on a normal desktop you need to run the other installer.
Daniel Ratliff
From: listsad...@lists.myitforum.com [mailto:listsad...@lists.myitforum.com] On
Behalf Of Rajan Hotmail
Sent: Wednesday, April 09, 2014 12:33 PM
Hello,
I have tried to install App-V client installation on local test system but
it getting failed with below error. After troubleshooting I found that there
are two versions of the client installer - one labelled RDS (Remote Desktop
Services) and one labelled WD (Windows Desktop), and On Desk
Simply password protecting the boot media is not sufficient?
Did you set the registry key value that should prevent you from needing to
clear the PXE request? (Or maybe I misunderstood that comment)
Have you considered doing this with a web service such as Maik's? It would
handle your requireme
End goal, get good data into sccm to allow rebuilds via F12.
Using a web interface
We don't allow rebuilds without some monitoring, therefore to restrict a
customers ability to F12 rebuild we use collections.
We populate the collection via a webtool; simply adding the computer
Perfect starting point, thanks Reto :)
Stuart Watret
Offshore - IT Ltd
From: listsad...@lists.myitforum.com on behalf
of Kehl, Reto
Sent: 09 April 2014 08:59
To: mssms@lists.myitforum.com
Subject: [mssms] RE: suggestions for automation, client import and check
Hi Stuart,
I have added an 'OSD' button to the webtools which allows to enter a machine
name, mac address and the desired OS to deploy.
Before adding to the collection I do some short check:
macAddress = Trim(txtMACAddress.value)
If Len(macAddress) = 0 Then
16 matches
Mail list logo
