Jump to content


Established Members
  • Content Count

  • Joined

  • Last visited

Community Reputation

3 Neutral

About Lagamorph

  • Rank
    Advanced Member

Recent Profile Visitors

809 profile views
  1. Unfortunately the reason I'm using standalone media is that the servers are more often than not connected to networks where DHCP is disabled at the switch level for security, so the task sequence can't contact any external server at all. And we have so many different internal network ranges that putting a script into the task sequence to configure a temporary manual IP isn't possible.
  2. Hi all, So I'm possibly looking to do the impossible here but thought I would ask the question. At the moment my standalone media prompts with a UDI wizard to complete details such as hostname, OU and security policies, but I'm currently working on a Powershell script to automate Offline/Standalone SCCM builds of physical servers which aren't able to connect back to the SCCM infrastructure, but where the iLO can be reached remotely. This script will prompt a user to input details such as a hostname and some other custom variables that are in the UDI wizard at the moment, then using HPEi
  3. Bit of a long shot and I suspect this isn't something that can't be done (at least not easily) but is there any way to find out what collections a machine in SCCM used to be a member of but is no longer? I've got a server that appears to have been part of a patching collection with a maintenance window, but isn't any longer, and I'm wanting to confirm it was indeed a part of that collection. Even more I'd like to see when the server was removed from the collection and by who if it were at all possible. Is there any record, either within SCCM itself or in the logs on the actual server, of
  4. Looking at the ClientLocation.log I think I see that it's a certificate issue, there are errors for, Failed in WinHttpReceiveResponse API, ErrorCode = 0x2f0c [CCMHTTP] ERROR: URL=https://<MPFQDN>/SMS_MP/.sms_aut?SITESIGNCERT, Port=443, Options=31, Code=12044, Text=ERROR_WINHTTP_CLIENT_AUTH_CERT_NEEDED Looks like I'll need to speak to some people who aren't back in the office until Friday
  5. Hi all, I've created a Task Sequence to deploy a non-domain joined Windows Server 2016 build however it fails whenever trying to install an Application with the following error, "Failed to run the action: Install Nagios Opsview. Required management point not found (Error: 87D00269; Source: CCM)" I've found this thread on the issue, https://www.windows-noob.com/forums/topic/10746-error-0x87d00269-when-installing-application/ , and I've put a step into the task sequence before the Install Application step to set SMSTSMPListRequestTimeout to 20 minutes (So the value was set to 1200
  6. It was posted to a website back in 2010, http://www.madanmohan.com/2010/11/how-to-find-clients-with-no-maintenance.html And the writer hasn't updated since 2013. The problem I'm having is if I paste that query into the Query language of the SCCM query rules, it just comes back with Syntax errors. As I say I've virtually no experience with writing queries and don't know where to begin with debugging it, or how to build a similar query using the query builder as I've no idea which options I'd need to be selecting. EDIT - Found where I was going wrong. The queries I've b
  7. Hi all, I've been tasked with creating a collection in SCCM that will run a query and add any servers with no maintenance window configured to the collection. This will allow us to then target those machines to get them added to the maintenance windows we want. Unfortunately building SCCM queries is completely new to me so I'm not really sure where to begin. The query builder is somewhat overwhelming with how many options there are available when presented with the Select Attribute screen. I have been direct to this query that was posted on another website, SELECT sys.Name0 'Nam
  8. Wasn't sure whether to post this here or in the SCCM 2012 forum in all honesty, but I'll try here first Ok, so in our 2008 and 2012 deployments via SCCM we have GPO Packs that were created before my time at the company for MDT deployments, so I was able to just implement these easily enough into the SCCM task sequence. We're currently running SCCM 2012 R2 SP1 with the Windows 10 ADK and MDT 2013 Integration. Now though, I need to create a new 2016 GPO Pack that we can apply during the SCCM Deployment task sequence (We don't use actual AD GPO, just local policies applied via GPO Pack.
  9. Sorry for the delayed response on this. There is no pid.txt file that I could see unfortunately, though after doing more digging I think I may have found the cause. Apparently with the last few versions of Windows, the installation on a non Volume Licensed copy of Windows cannot automatically bypass the Product Key entry with no product key specified in the Unattend.xml, even when deploying via SCCM, this functionality is only available on Volume License versions. As I'm just using the Windows Server 2016 trial ISO at the moment, which won't be a Volume License version, it may not yet poss
  10. Hi all. I know Server 2016 is still in Technical Preview, but we're beginning to do some work on testing deployment via SCCM. Whilst on the whole it's been successful, whenever we do the deployment it hangs at a screen prompting to enter a Product Key. We can manually select the option to Do it later and the deployment continues as normal, but obviously this is hardly a long term workable solution. Does anyone have any ideas on how we can automatically skip this? Below is my customsettings.ini, [Settings] Priority=Default Properties=MyCustomProperty [Default] OSInstall=Y SkipCapt
  11. Hi all, So this is kind of following on from a previous thread where I was having trouble with installing an MSI during a deployment task sequence, where the installation would just hang endlessly. Oddly this only occurred on physical servers, deploying to VMs worked fine and the installation script worked fine outside of SCCM with no boxes popping up. I decided to try a different approach to resolve the issue and instead of a package I thought I'd make use of the new SCCM Applications to try and install the MSI, but I'm experiencing a new issue with this. Whenever I try to install the ap
  12. Sadly adding this script didn't make any difference. The deployment still hangs when I attempt to deploy that package. As before it doesn't appear to ever start installing, just hangs endlessly with "Waiting for Job Notification" I'm hoping to get the SCCM environment upgraded to R2 soon, so I'll do that and rebuild the Standalone ISO and try again. Hopefully this is just an SCCM bug that's fixed somewhere after SP2, it doesn't strike me as being the package itself since it never even starts to run the installer and it's not doing anything special, just using msiexec.
  13. It's because the task sequence is essentially a "unified" sequence for different environments, so different applications (or versions of applications) will be installed as part of the deployment depending on which variables are selected using the UDI wizard at the start of the task sequence. As I said the install.wim has been updated with Windows Updates using the built-in SCCM tools, so it's not quite a 'from scratch' deployment. I did experiment with using a Captured image initially, but no matter what I did the Task sequence would always immediately exit after reaching the SCCM client i
  14. Just incase it's relevant, I've had a look at the execmgr.log and it contains only the following, Policy arrived for child program Universal Forwarder 6.3 x64 ExecMgr::GetTaskState - GetTaskState Failed with error code 0x87d00317
  15. I've had a read through that but I'm not sure it's quite the same issue I'm having. That article references deploying a captured image, which this isn't. The task sequence is deploying an OS from a .wim file pulled directly from an Installation ISO (Though it has had windows updates included via SCCM) and the Package I'm installing isn't the first one, it's the very last one after multiple other packages have installed successfully. The package has been hanging for longer than 12 hours as well, it begun hanging at around 5:40pm yesterday evening and was still waiting at 8:30am this morning.
  • Create New...