Jump to content


SCCM4EVA

Established Members
  • Content Count

    15
  • Joined

  • Last visited

Community Reputation

0 Neutral

About SCCM4EVA

  • Rank
    Member
  • Birthday 06/02/1974

Profile Information

  • Gender
    Male
  1. Hi all, I need to migrate my SCCM 2007 R2 Central Server (running on Windows 2008 Standard x64) to a new Win2008 R2 Server. I have version 4.00.6221.1000. It is parent to two child Primary sites (on Windows 2008 Std x64). The existing server is having issues but is still up and running. I also want to install SP2 in readiness for Windows 7/2008R2 deployment The SQL database it is pointing to is staying the same. Has about 2000 clients and in a single 2003 domain The Central Server has collections, boundries, packages, OSD's and advertisments. It is also the FSP / MP / SUP and Repor
  2. Hi all, I need to migrate my SCCM 2007 R2 Central Server (running on Windows 2008 Standard x64) to a new Win2008 R2 Server. I have version 4.00.6221.1000. It is parent to two child Primary sites (on Windows 2008 Std x64). The existing server is having issues but is still up and running. I also want to install SP2 in readiness for Windows 7/2008R2 deployment The SQL database it is pointing to is staying the same. Has about 2000 clients and in a single 2003 domain The Central Server has collections, boundries, packages, OSD's and advertisments. It is also the FSP / MP / SUP and Repor
  3. Hi, I have an issue with boot files not distributing to DP's. This is my error log from SMSTS.log (see below). However this is my question. Should the modified date of a boot.wim file change when you inject new drivers/change to enable support testing etc? (in the smspkgd$ and smspxeimages$ folder) - I can inject drivers into a boot.wim but can only distribute via the schedule and not via manually updating distribution point (get error about not finalized boot file) - IT appears to disctribute (messsages sa so) but nothing on the DP point. Filtering Content Locations. TSPxe 21/04/
  4. Ok, so I have re-added as a protected DP, how can I tell that my clients are using this DP to download my package?
  5. ok thanks, I've deleted the role from my local server and will re-add as a protected DP and specify a couple of subnets.
  6. hi Team, I am deploying a MS Hotfix via package deployment. I have created the package and configured the program within it. I have also deployed to several distribution points (servers). How do I ensure the package is pulled from the closest distribution point (server) and downloaded to CCM\cache folder of the PC's I am deploying to. It seems my package which is only a few hundred kb seems to take ages to download and run on the PC. CHeers
  7. I have now manually recreated the SMSPXEIMAGES$ folder and SMSPKG folder under that. I have pushed some boot files down from my Central site server. I am still getting the error: "PXE Control Manager detected PXE service Point is not responding to PXE requests. The error is 16389". Would it be best to remove any packages and re-install the PXE service point component from the SCCM server?
  8. Won't deleting my remoteinstall folder delete all my packages/images etc? I have successfully reinstalled it now with a new d:\remoteinstall directory. the SMSPXEimages should recreate then?
  9. this is an iscsi drive too. Could be a timing issue.
  10. it seems all my shares on the D:\ keep dissappearing. This is odd.
  11. I did, and this is the point I am at where I can't configure the server as a WDS Server.
  12. It they appeared after a reboot, Sinbce the WDSServer was trying to start.
  13. IT did, I have deployed packages before. I am sure of it. However it would seem but then has been failing with increased regularilty. Looking through the Windows Deployment Services logs it would seem that it was been trying to startup and then it shuts down on a regular basis Erors include: ID 783 BINLSVC An error occurred while initializing the Auto Add database. ID 261 WDSPXE An error occurred while trying to initialize provider BINLSVC loaded from C:\Windows\system32\binlsvc.dll. If the provider is marked as critical the Windows Deployment Services server will be shutdown. --
  14. Firtsly, great site anyweb. Your instructions are fantastic, I have several SCCM servers in our environment at present. However my Primary SCCM Server, the WDS server service wouldn't start. Running this on Windows 2008 Standard I unsinstalled WDS and have reinstalled however I am unable to 'configure' the WDS server. IT simplay errors after trying to complete. I selected the same D:\RemoteInstall folder as before and choose respond to any client when configuring I hadn't removed the PXE Service Point either (I think I should've done this first) I am wondering what steps to take as hav
×
×
  • Create New...