Jump to content


chimmez

Established Members
  • Content Count

    12
  • Joined

  • Last visited

  • Days Won

    1

chimmez last won the day on June 11 2015

chimmez had the most liked content!

Community Reputation

1 Neutral

About chimmez

  • Rank
    Member
  1. Hi everyone, just a quick and strange bug. I have a captured Windows 10 1511 ENT wim, which is clean except for the removal of a few 'modern' apps (i.e. Xbox etc). This wim is being deployed from SCCM Current Branch and is a really basic task sequence (nothing too complicated going on, just the regular deploy ts). The systems are then being joined to the domain. After about 30 minutes, the date and time of the system reverts to when the Wim was captures (last Friday). Not only does the system time change, it changes the time in the BIOS of the machines. The system gets the correct time at the time of deployment. An Event ID of "1" gets logged, that simply says that the reason for a time change is "An Application or system component changed the time". Any ideas why this would happen? Seems a little odd.. Thanks!
  2. I am already on 2012R2 SP1 (aka 2012 SP2). I upgraded before the Windows 10 ADK was available publicly. Can I just uninstall the 8.1 ADK and install the 10 ADK, or do I have to follow the process listed above in your excellent guide, except for the installation of SP2? I've found this article (http://blogs.msdn.com/b/beanexpert/archive/2015/08/05/how-to-switch-to-windows-10-adk-on-configmgr-2012-r2-sp1.aspx), would you recommend that, as it seems that this is the upgrade path that I'm after. Cheers! EDIT: Actually, scratch that - I've found this (http://blogs.technet.com/b/configmgrteam/archive/2015/08/05/windows-10-adk-and-configuration-manager.aspx), which you have posted on a previous post of mine. It has cleared it up: Download the Windows 10 ADK. Uninstall the Windows 8.1 ADK from your site server(s). Install the Windows 10 ADK on your site server(s). Restart your site server. (This ensures that components such as the WIMGAPI driver are properly registered for use with Configuration Manager.)
  3. Just a quick update - by following the steps that you provided in the link above (http://www.niallbrady.com/2013/10/09/how-can-i-manually-add-winpe-5-boot-images-to-system-center-2012-configuration-manager-sp1-cu3/) I was able to get SCCM 2012 R2 SP1 to PXE boot using the Windows 10 ADK and the new version of WinPE. All that I did was use the 10 ADK toolkit environment, and, modify the targets for the packages to: dism.exe /image:c:\WinPEMount\x64 /add-package /packagepath:"C:\Program Files (x86)\Windows Kits\10\Assessment and Deployment Kit\Windows Preinstallation Environment\amd64\WinPE_OCs\WinPE-Scripting.cab" dism.exe /image:c:\WinPEMount\x64 /add-package /packagepath:"C:\Program Files (x86)\Windows Kits\10\Assessment and Deployment Kit\Windows Preinstallation Environment\amd64\WinPE_OCs\WinPE-WDS-Tools.cab" dism.exe /image:c:\WinPEMount\x64 /add-package /packagepath:"C:\Program Files (x86)\Windows Kits\10\Assessment and Deployment Kit\Windows Preinstallation Environment\amd64\WinPE_OCs\WinPE-HTA.cab" dism.exe /image:c:\WinPEMount\x64 /add-package /packagepath:"C:\Program Files (x86)\Windows Kits\10\Assessment and Deployment Kit\Windows Preinstallation Environment\amd64\WinPE_OCs\WinPE-MDAC.cab" dism.exe /image:c:\WinPEMount\x64 /add-package /packagepath:"C:\Program Files (x86)\Windows Kits\10\Assessment and Deployment Kit\Windows Preinstallation Environment\amd64\WinPE_OCs\WinPE-NetFx.cab" dism.exe /image:c:\WinPEMount\x64 /add-package /packagepath:"C:\Program Files (x86)\Windows Kits\10\Assessment and Deployment Kit\Windows Preinstallation Environment\amd64\WinPE_OCs\winpe-securestartup.cab" dism.exe /image:c:\WinPEMount\x64 /add-package /packagepath:"C:\Program Files (x86)\Windows Kits\10\Assessment and Deployment Kit\Windows Preinstallation Environment\amd64\WinPE_OCs\WinPE-WMI.cab" Strangely this has also dramatically increased the speed in which OS WIMs images are downloaded from my SCCM server - it now maxes the server's upload (1 gigabit/sec), whereas with the previous boot images that I've created, it was generally capped to 100 megabits/sec, which has been an annoying problem on our production SCCM server since the R2 update (ie, it was really quick in SCCM 2012, R2 up to and including CU3 seemed to slow OSD down considerably). Thanks for your help!
  4. Thanks for the link, I'll give it a shot now! As far as where I found that R2 SP1 supported the Windows 10 ADK, I swear that it was posed on technet under which ADK is required, something like "A minimum of the Windows 8.1 ADK, and the Windows 10 ADK is now supported", however I can't find it now. Furthermore, this photo (http://i2.wp.com/ano...-R2-SP1-SP2.jpg) shows that the 10 ADK is at least going to be supported. No big deal anyway, just keen to try some new System Center stuff! Thanks again.
  5. Hi all, I'm interested in seeing the current state of Windows 10 deployment using SCCM 2012 R2 SP1 in my lab. However, I'm running into a little bit of trouble. Firstly, I'm running SCCM 2012 R2 SP1 (ie, the latest version), which was upgraded with the Windows 8.1 ADK. Since then, I've downloaded and installed the Windows 10 ADK (https://msdn.microsoft.com/en-us/windows/hardware/dn913721.aspx - right at the bottom). My first issue was that 'copype.cmd' wouldn't work, but I fixed that by manually inserting some variables into the a copied script called 'copype-test.cmd'. As we all know, this creates a winpe folder wherever specified. From there, I grabbed the winpe WIM from the sources folder, and imported it into system center. This is what I assume to be WinPE10. However, although it is distributed, and then deployed from the PXE site server, clients will not boot using it. If it is the only boot.wim on the PXE server, a client will simply sit at the PXE service screen, and if it is just the last boot.wim image to be deployed from the PXE site, clients will use the old, 8.1 boot image. Furthermore, if I check the properties of the WinPE 10 boot.wim, I don't get the usual options (ie, add drivers etc) that one would usually expect from the properties dialog. Have I had a brain-fade and forgotten a basic step when importing a boot image? Or, is this an issue with using the Win10 ADK (although I did read that SCCM 2012 R2 SP1 did support the new ADK...) I'm not at work for another 14 or so hours, but I can VPN in if someone has an idea of what the issue could be. Thanks! Chimmez.
  6. Just to a Virtual Macine at the moment; i can try a physical, however I thought that it would be fairly redundant.
  7. Have done so; I created a barebones TS that was only the OS, boot image and the ClientUpgrade 5.0 ALL packgae, all have been redistributed the the DP multiple times just to be sure.
  8. Hello, This forum is great, and I really appreciate all of the help that you guys have provided me! Bu I still have problems, so here goes; I have successfully deployed OS's for the past couple of weeks, there have been some sporadic issues that I have come across, however I have usually been able to fix them by creating a new task sequence. I am running SCCM 2012 SP1 under server 2012. Now however, I am receiving an error message "An error occurred whlie starting the task sequence (0x80070570)" This appears as soon as I start the task sequence - ie as soon as the checking dependencies screen goes away. I have my SCCM server running in a virtual machine, so I can simply revert to a previous state; however I would like to solve the underlying issue, as it might come back even when I revert. There is no log that I can find, is SMSTS.log, so I dont think that there is any more information that I can provide; however if there is anything that you wish me to upload I can. I have tried using different OS images and installers, and I receive the same error code. I don't know if it makes any difference, but a problem that I was having was after creating a task sequence, it would work fine, but if I left it for a couple of days, running the task sequence would error out and say that boot image could not be found on the DP.. This would be fixed after recreating the task sequence. Thanks again! Jorden.
  9. Hello, Real quick question; hopefully there is a really quick solution too! First things first, I have managed to deploy my Windows 7 and Windows 8 images perfectly across my domain, and they are all functioning fine. The problem that I am getting is that after a period of time, if I boot a PC via PXE, and I choose my task sequence, the task sequence will fail on checking dependencies, and complain that it cannot find P001005 (or something similar) on the DP - which is the x64 boot.wim.... which it needed to boot into WinPE in the first place! The strange thing is, that if I simply recreate the task sequence, it works.. but only for a day or two and again it fails with the same error. Just to be clear, the PXE booting stage works fine, its simply when the task sequence starts to run, the dependency check fails. Any ideas? Thanks for the help!
  10. Sure thing! thanks for the assistance. Cant find the log that you are talking about; could it be the ccmsetup log? I have attached in any case, as it may be relevant. ccmsetup.log Thanks again!
  11. Hello, I love all of the tutorials on this site; extremely helpful and easy to follow. I have run into a slight problem though; I am up to the Build and Capture process of Windows 7. By following the guides, SCCM 2012 SP1 will deploy the OS to my virtual machine, however it just seems to skip the capture process, leaving me without a capured WIM. I can still use the virtual machine, it just leaves me with a blank copy of Windows 7. I have attached the SMSTS.log file just for reference. smsts.log According to that file, the process fails when trying to install the sms client is trying to be installed, and for the life of me I cannot work out why!... Could this be a permissions issue somewhere? I have made sure that the Network Access Account has access to \\sccm01\sources\caputres - so that shouldnt be any issue. A weird thing that I have noted however is that the path \\sccm01\SMS_P01\Client is inaccessable to my SMSadmin account - even going as far as saying that I do not have the permission to even view who the owner of that folder is. Probably not relavant, however as the client package pulls information from \\sccm01\SMS_P01\Client, I thought it may be insightful. Thanks for your help everyone. and especially anyweb for his awesome guides! smsts.log
  12. Hello, Just a bit of background information: This is a school environment, servicing around 150 PCs. The new environment will have two main servers; AD-1 (A new server, 32gb Ram and Dual Xeon Procs) and our current server P-01, (Older Xeon machine, 12GB Ram). AD-1 is going to be the single domain controller for the domain, and I am hoping to get SCCM 2012 running purely from the older machine. I wish to use Server 2012 on AD-1, and am willing to use 2008R2 on P-01 as SCCM2012 is not currently supported on Server 2012. This will be a clean slate; I will be starting the whole thing from scratch by wiping all of the data from the old server. What I need to know: I have read all of the guides which have been posted on this forum with regards to setting up SCCM2012, and I have successfully created a test environment identical to the guides provided (with a few little hiccups, of course). However, what I would like to ask is: 1. Does the SCCM 2012 server have to be a domain controller, or is this recommended at all? 2. Will P-01 be able to communicated properly with AD-1 if AD-1 is using Server 2012? 3. As I need to extend the AD Schema on AD-1 for SCCM2012 to be functional, is this possible from Server 2012? (ie, if the functional level of the domain is 2012, or would I need to set the functional level back to 2008) 4. The RTM Guides for setting up SCCM 2012 are specific for a CAS setup; I only require a Primary Site setup, and thus have been using the guides from the release candidate; however, at the top of the guides, it suggests that they are not up to date, and to use the newer guides that are only for CAS setups. Am i missing something, or should I just keep using the guides from the RC? Thanks in advance everyone, your help is highly appreciated.
×
×
  • Create New...