Jump to content


ranjb

Established Members
  • Posts

    6
  • Joined

  • Last visited

ranjb's Achievements

Newbie

Newbie (1/14)

0

Reputation

  1. Hi Everyone Currently have a new environment on 2002 CB with 1 site server and 1 DP. Just performed a source hierarchy migration from a 2002CB. It seems most app deployments are successful in the new hieracrchy however when deploying packages I run into an issue. It seems deploying just to the DP it fails but when deploying to both primary server and DP it succeeds. The site server also acts as a DP. When looking at the distrmgr log all is successful from that perspective but when reviewing the pkgxfermgr I see some errors. ExecStaticMethod failed (80041001) SMS_DistributionPoint, FinalizeContent CSendFileAction::SendContent failed; 0x80041001 When reviewing the smsdpprov log on the individual DP it shows the following: MoveFile failed for \?F:SCCMContentLibDataLibCS1003BE.3.temp to \?F:SCCMContentLibDataLibCS1003BE.3 FileRename failed; 0x80070002 CContentDefinition::Finalize failed; 0x80070002 Failed to finalize content ‘CS1003BE.3’ for package ‘CS1003BE’. Error code: 0X80070002 I attach a screenshot when reviewing the error on the monitoring window. I have added the primary site computer account as a local admin to the DP. Anything else I might be missing here? I did try to restart WMI services and check permissions but all looks ok to me as per this blog: https://smsagent.blog/2017/04/24/configmgr-content-distribution-fails-with-0x80041001/
  2. Hi Sorry this is a duplicate post as I mistakenly posted in the CM2012 forum. I am currently doing a source hierarchy migration from 2002CB to 2002Cb in 1 forest trust with 2 domains. I done in a way so that the new site server mirrors the old one as much as possible. Apart from the server OS which is 2016 as opposed to 2012 in the old environment. What I am trying to achieve is a solution which isn’t going to cause too much downtime for the client as they have 3000 devices to service through MECM and want to do it with the least amount of downtime possible. I am at the point where the source hierarchy is now migrated and I am using the ConfigMgr content source update tool to point and copy binaries to the new location which is currently in progress. If I was to create a new DP against the new site code, as the new site server can see the source site server (on the same subnet) could I make use of the pull distribution point to effectively stage the content from others DPs to my new DP and then once I have tested content from this new DP with a client I can slowly decommission the old DPs. Would that a workable option? There are 4 DPs in the source and I can see they are all eligible for re-assignment however my question is if those servers sit in the old domain but I need to move those servers in the new domain. What would be the best approach? I assume the only way would be to recreate those DPs in the new domain against the new site code? Is there a way to migrate DPs from source to new destination DP or is it case of introducing the new DPs in the destination hierarchy and then just ensure they have the DP role and then ensure the content is populated onto that DP before the old is decommissioned? Also currently the old DPs are serving PXE for OSD deployment so I believe before that is done the DHCP or switch helpers will need to point to the new DPs so that process can continue, would that be correct? I look forward to any responses. Thank you
  3. Really useful thread here as I am currently doing this with a client on CB2002 to CB2002. I do have some questions though which I am unsure about which I am hoping someone can validate for me. I am currently doing a source hierarchy migration from 2002CB to 2002Cb in 1 forest trust with 2 domains. I done in a way so that the new site server mirrors the old one as much as possible. Apart from the server OS which is 2016 as opposed to 2012 in the old environment. There are 4 DPs in the source and I can see they are all eligible for re-assignment however my question is if those servers sit in the old domain but I need to move those servers in the new domain. What would be the best approach? I assume the only way would be to recreate those DPs in the new domain against the new site code? Is there a way to migrate DPs from source to new destination DP or is it case of introducing the new DPs in the destination hierarchy and then just ensure they have the DP role and then ensure the content is populated onto that DP before the old is decommissioned? Also currently the old DPs are serving PXE for OSD deployment so I believe before that is done the DHCP or switch helpers will need to point to the new DPs so that process can continue, would that be correct? I look forward to any responses. Many Thanks
  4. Hi all I am in the process of performing a mecm migration using source hierarchy approach. The current environment is on current branch 2002 with 1 primary site and 4 DPs, no SUP. The plan is to create a new destination primary site but share the existing DPs as they don't have capability currently to move the DPs to new domain. Main objective is to get comanagement working as currently this isn't possible with server in old domain due to some legacy issues. Does anyone have any sources on how I could do this step by step? Many thanks
  5. Hi We currently deploy Windows 7 using an unattend.xml and the mechanism is using WDS on a 2008 r2 server. We have a number of different machines comprising of laptops and desktops, I am finding that all the correct drivers are not being picked up once the image has been loaded onto the client. An example is the graphics card is not working on 1 particular machine unless I manually install this using the CD after it has loaded win7. I am aware that using WDS I can integrate all of our drivers for all builds of machines (e.g. NIC card, graphics, sound drivers etc) and WDS will decide which driver goes for which build. I would like to do this but am struggling to get it working. I was wondering if others had similar issues like mine? Are there any weblinks for documentation which will allow me to do this? I am also looking at installing System Center R3 for us to do zero touch deployment of Windows 7 with the ability to schedule the installation of Windows 7 over a weekend. We will be overseeing this but it would be great if we could leave it running overnight and come in the next day to do checks and fill in computer names etc. I would like to do this in a way that involves less intervention from us on the client end if possible. Currently using the unattend.xml we only need to enter a computer name. I plan to also install System Center on the same server as our WDS and MDT server which is 2008 R2 in a VMware cluster. Is this ideal or would I be better using a separate server just for sccm? I can create another server if this is necessary but thought I would ask for a second opinion. I am also been reading and am aware I will need to do some schema changes to the AD infrastructure. If anyone has guidance or web links on how best to do this that would be greatly appreciated. Our plan is to rollout Windows 7 to 170 machines over a weekend. I am interested in also know how much load this would be on the WDS/MDT server. We have setup WDS with multicasting in mind. Has anyone tried rolling out Windows 7 on lots of machines all at once. Does Multicasting manage the process successfully, reason I ask is it is my intention to install windows 7 on as many machines around the building, leave the process going overnight and come back the next day to check on progress, hoping that all machines have the correct WDS image and is ready to roll. Any advice on all/some of these questions would be most appreciated. Thanks
  6. Hi Was wondering if someone can help. We have a bare bone customised image of WIndows 7 enterprise on a new WDS server we created. It runs on Server 2008 R2 so has the extra features of WDS such as driver injection but when we boot via PXE on a few laptops and choose the image, it begins the progress bar but then just says "windows is loading files" and just hangs there. It only seems to be with 2 specific laptops which have a CLEVO motherboard, other desktops and laptops seem to be fine. We have injected the proper network and chipset drivers into the boot image. There wasn't a BIOS update needed for these laptops. Whats odd when it boots up WDS it tries to load x64 WDS. We have WDS on a x64 server,is this why it is happening? Has anyone had similar issues like this. All I want to do is put a customised wim file onto a laptop. Is there a way I can use imagex to deploy a wim file. I tried to do it with imagex /apply but it failed. Any advice would be most appreciated. Thanks
×
×
  • Create New...