Jump to content


jpboyce

Established Members
  • Posts

    6
  • Joined

  • Last visited

jpboyce's Achievements

Newbie

Newbie (1/14)

0

Reputation

  1. Hi Trevor, There's nothing at all in the IIS logs for the secondary site server. I can't see any references to the new server in the IIS logs on the primary server. The sender address is using the NetBIOS name (as is all the other secondary) I"ve managed to progress is now though so that the new site is appearing. However, I"ve run into a new issue relating to server shares. There's two server shares setup on the secondary site servers. I've set these up on the new server, but when I try to copy a package, it only lists the "root" server (ie. servername), it doesn't list server\sharename in the list of distribution points.
  2. Hi all, I'm currently trying to setup a secondary site SCCM server for a new office. The server is running Windows 2008 R2. I've added all the prerequisites as per the documentation and when the installer runs, it doesn't find any problems. However, after installation is complete, it's like the server hasn't communicated back to the primary server. Symptons of this include: * The new server/site doesn't appear in the sites list in the SCCM console on the primary * I'm seeing almost zero traffic flow between the new secondary and the primary server * No activity in the Inbox folders Is there any sort of known issues that might cause this? I've tried turning Failure auditing on for the new secondary server in case it was a permissions issue but I'm not seeing anything coming up in relation to SCCM. Any ideas, suggestions, etc? Thanks.
  3. Just following up on this, I think I've narrowed down what is causing the error to appear. In the XP SOE task sequence that already existed, there was two task items relating to setting the computer name. One would set the variable OSDComputer to a period (.). The second would run a VBscript that would interrogate the machine for it's asset tag entry in the BIOS via WMI. The script would then assign that value to the OSDComputername variable and the OS install would inherit that. With the Windows 7 deployment, I've tried using the same task setup and when either of those tasks are in place (both or one at a time), it will fail with the error. If I remove them, the OSD finishes but the machine has a random name (MININT-randomletters). Is there any reason why setting the OSDComputerName variable via the script would cause it to fail? Thanks.
  4. It's being done as an "Apply Operating System Image" task using the "Apply Operating System from original installation source". This option then references a Windows 7 package that had been added under Operating Systems Installation Packages. Attached image shows the task sequence at the moment (which I've recreated from scratch again) with detail of the apply OS image item.
  5. I'm installing 32-bit Windows 7. All the component lines in the unattend file I created had processorArchitecture="x86". It's not really an issue anymore of getting the unattend file to work anyway. I just want to be able to get my task sequence to work at all, as I mentioned, the error keeps appearing after I removed the reference to the unattend file.
  6. Hi, I'm trying to deploy Windows 7 using a custom task sequence on SCCM 2007 R2. Originally I had a basic task sequence that performed tasks such as formating/partitioning the disk, applying the OS image, Windows settings, etc. I needed to change the default language settings from en-US to another setting and tried using an unattended.xml file to do this. I added the file as a package in SCCM and then added the reference to it in the Apply Operating System Image task. After I did that, I started getting the error Windows could not parse or process the unattend answer file for pass [specialize]. The settings specified in the answer file cannot be applied. The error was deteted while processing settings for component [Microsoft-Windows-Shell-Setup] Where it becomes strange is I've tried to remove the reference, even removed the files from the package source folder and updated the distribution points, yet the error keeps happening as if SCCM is caching the values in it. Does anyone know what might be causing this or how I fix it? Thanks.
×
×
  • Create New...

Important Information

We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue.