neonetman

So was there any replacement for it, or a 3rd party alternative?

Morning all, We currently use SC VMM 2008 with the web-based slef service portal to allow our students access to a sandboxed domain and windows client for their coding work. I'm in the process of upgrading our estate to SC 2016, however I can't find the self service portal for this anywhere. Can anyone advise if this is available, if I need to use the SVMM2012 portal, or if I need o stick to upgrading to VMM2012 Cheers!

We seem to have WDS randomly stopping for no know reason. A restart of the service usually solves it, or occasionally it take a server reboot. Can't fathom out why this is happening

After a long and arduous process of getting our SCCM migration working, I'm now down to the last issue, which is getting SCCM to sync th WSUS update. It seems to have pulled a few updates in, but is now giving the following:- wcm.log give this error:- The server has unproxied access to the web Any thoughts to save a semi-mad NM from total insanity?

Thanks for your help Steve - as to what we're doin - that would be bimbling through with the blind leading the blind. Thankfully, I've jsut about got it cracked now

I've tried with both a device that's migrated (although it has no MAC address in it), and also with a complete unknown. We have no TS applied to unknown computers (nor did we on our last server) If I assign a task sequence, and imprt the PC it will run the TS, so I know DHCP/PXE is working. What I'm used to getting (from the old server, and from this one before I migrated data in) was what is in the screenshot below, however I'm not getting that

No that I can see - but as a reasnably newcomer to SCCM I'm not sure if I'm missing something

Sorry - I'm not explaining very clearly:- When I first installed SCCM on the new server, if I PXE booted a PC (before I created any deployments/task sequences), it would contact the server, look for policy, the go to abortpxe I then added a device, assigned a required task list. The device booted and ran the task sequence as planned. If the same machine booted again, because it had the PXE flag set, it would again contact the server, look for the policy and the go to abortpxe Now, after migrating all my content across from the old server, machines that are not registered do not come up with "looking for policy" and then fail to abortpxe - instead they just get no boot filename Obviously I assume that getting the boot file, and then going to abortpxe is the correct behaviour, as that was the default prior to migrating data in - yet I can't find out how to get back to that

Should it not pick up the "abortpxe" boot if there's no task sequence assigned? That's what it did before I migrated data. It currently sites for about 30 seconds before it decides it's got no filename

I've installed a working SCCM CB server, and tested some sample tasks sequences to ensure everything was working (whcih it was) I've now migrated all my collections, software, deployments etc from my 2007 server,and am now having an issue with PXE booting one of the PCs When I power on, it sits for ages before coming up with no boot filename received When i check the system status messages in the console I get the following:- The PXE Service Point intructed device to boot normally since it has no PXE deployment assigned.. I initially had this device in a collection with a PXE enabled task sequence, however I've now deleted it as I would expect an unknown machine to get the "abortpxe" boot. I'm so close to getting sorted, yet I seem to have hit a brick wall with this Can anyone suggest? Cheers

Afternoon all, Finally had a breakthrough and got eh new SCCM up and working. I'm now migrating what we need from the old server to the new. I've found a couple of utilities that will update the source location in each package, and copy the source files to the new server. The issue I'm still trying to suss, is getting all the migrated content pointed to the new ditribution point - I can do it manually, however it'll be a major pain to have to do each individual package and driver package individually - is there a way of simply adding *every* package to the new dp automatically?

UPDATE:- I'd missed adding a boundary group.. Once I added that, everything started to look a lot more rosy. I've hit a couple of issues since with the "error 50 - not supported", however I'm thinking that's because I'm trying to install software without having the SCCM client installed first. Watch this space, and thanks for the help!

Yes - that's enabled on both.

After a few more attempts, I've flattened and rebuild my SCCM server, and am now having problems geting past the inital PXE boot - I've opened a new thread with the current issues. I'm tearing my hair out! Thank you for your help so far, and I'm hopefll you can assist on the new thread Cheers

I've flattened and re-installed our SCCM server as I couldn't get past the problems of a dodgy migration. I've got the system running in so far as I can PXE boot a client, however immediately after flashing up "preparing network connections" the PC reboots. I've added the rlevant network drivers to the boot image, so I'm at a bit of a loss what is causing the issue. I'm getting the following in the SMSTSlog:-

I've 3 scripts in total - login, logout, and "startup" which adds the PC to the database if it doesn't exist, and clears any remaining logins at startup

Uses NTLM authentication to identify the pc name and username and then logs those to a MySQL database to give us a quick overview of PC usage and who's logged in where. Staff can then access a page on our intranet showing a list of free PCs

Do I need a final restart at the end to boot back into Windows for the user?

smsts.log.txtI've tried simpifying the task sequence right down to installing Windows and setting administrator account (see pic) but am now getting an error 0x80004005. I've attached the Console log as well as the client log file in the hope you can help , andsmsts.log.txt

That's the strange thing - I am setting them, and it says it's applying but doesn't seem to be aplying right....

It's not enabling the local admin account so not got logged in yet.

It's exactly the same

I've trying to build a machine in SCCM current branch, and am having problems with an error at the point I tell it to join the domain - I'm getting the following error:- The task sequence execution engine failed executing the action (Join Domain or Workgroup) in the group (Apply Domain Network Settings) with the error code 50 Action output: . The operating system reported error 50: The request is not supported. The task sequence is simplistic so far, so no idea why this is happening:-

I've trying to buidl a PC using a pre-existing tasks sequence that we know works. The PC is booting from PXE, but then failing before staging the boot image. The error in the SMSTSlog file is Content location request for STB003A5:3 failed. (Code 0x80040102) TSPxe 03/11/2017 12:25:58 1304 (0x0518) I've already deleted the package with ID STB003A5, and removed the reference to it in the task sequence. Can anyone advise whhat I've missed that would cause this?

I'm wanting to silently call a PHP script on an internal webserver from each PC as it logs on, and then a different script at logoff. I'm wondering if there's a way to call these using GPO's? Can anyone advise?