Jump to content


Established Members
  • Content Count

  • Joined

  • Last visited

Community Reputation

0 Neutral

About Sisko

  • Rank
  1. Hi guy's, I know that when you're replicating data between servers/sites, its recommended that you set the staging folders to be "double the size of the data being replicated" to avoid replication delays as I've read on Microsoft's site. Does that mean double the size from the top level folder? So, if you have a top level folder being replicated to other sites, and its 15GB in size, but you only have it set with a 5GB staging quota, then it's going to cause delays. Should you have the storage quota double the 15GB size of the folder?? Cheers, Sisko
  2. Hi guy's, not quite sure where to post this but figured this might be ok since its a Server 2012 box I'm on. I'm trying to implement a signature to be deployed via group policy. I've got all the Office 2013 Admin templates successfully working, but there only seems to be an option to DISABLE the use of email signatures in Outlook 2013.....there doesn't seem to be an option within the templates for setting one up. Can anyone point me in the right direction if possible? Cheers, Sisko
  3. Hi guy's, when you delete expired updates from a Deployment Management container, are they then removed from the server upon deletion from the package? I'm going through our system and tidying up all our old expired updates/deleting old deployment packages etc and just want to be sure. I'm clearing up old Update Lists also, I'm aware that these are just lists for information purposes really, so deleting updates from these doesn't have any impact at all on deployments. Thanks, Sisko
  4. I think this is the problem I've been having with my Dell OptiPlex 7020 machines when trying to image. The only thing that I can tell is, I am using the same driver throughout the image process for the WinPE and OS Deployment, the driver never changes (because this is the only driver the machine will accept in Windows, and also the only driver that allows WinPE to boot successfully), yet I still lose my IP address during the imaging phase and then it fails right near the end.
  5. Found a workaround for now. If I deny read access to the desktop.ini file within the user's home drive folder, it displays the folder correctly on the share. Not ideal having to go through 28 user folders, but, I guess it will do for now. Way to go Microsoft, apparently they say this is a "feature" from several articles I've read on this topic.
  6. Hi guys, I've noticed on our system that our user's home drive folders while being successfully re-directed to our main file server, the names of some of the users are not showing up with their name. To give an example would be Joe Blogg's home drive folder shows up as Jack Black on the user$ share we have, where all user home files are stored. Yet when you go into said folder, you get the correct user's name displayed in the file path. I don't recognise the folder icon being displayed either, so not sure what it means. Also, its worth mentioning that we archive off user's data when they leave, the data is shifted off the main file server and onto a Netgear NAS box for archive purposes, so its on a totally separate box. BUT, when I changed the folder name on the Netgear box......all the named folders on the main file server changed too to reflect the name change?? How can that happen when they are on totally separate network devices? Are they "connected" somehow?? As it stands just now, I have to go through all the folders in the attached screenshot till I get to the right folder for a leaver before I can archive off the data. Has anyone ever seen anything like this before? I've attached a small screenshot for review. Thanks, Sisko
  7. I think I'm going to have to speak to Dell about this. I'm stumped and its still on going, I've just not looked at it for a couple of weeks. If the NIC drivers are in the WinPE boot image, and it runs everything fine up to a point, I can' see how or why the machine seems to be losing its IP address and then throwing the image process into disarray. All our other model PC's image perfectly fine, all the OptiPlex 7020 drivers have all been successfully imported into SCCM, I've seen the task list complete successfully where it installs the drivers, so.....again I'm scratching my head. Still the same for the other OptiPlex 7020 machines I have tried to image too. Can anyone offer any other input at all? A rabbit out the hat miracle?
  8. Hi Pete, I have taken all the drivers out of SCCM and split them up so that only 32bit drivers are being used, just incase there was a conflict being caused somewhere, as before, I had 64 and 32bit drivers mixed together in the one package. I also removed the entry in the task sequence to install the drivers, I figured I would let SCCM choose to install them automatically from the driver store instead of running an entry in the Task Sequence. So, after re-creating the package, updating the dist point, making sure the correct NIC driver is in the WinPE boot image and that only 32 bit drivers are packaged, it still goes through the image process, but it falls over after the second reboot, when its sitting at the black screen saying "Setup is preparing your machine for first use" I think it is, the SCCM dialogue box pops up and it tries to run one of the toolkit packages, it sits there about five minutes or so, then fails with the (0x800700002) error, which in the logs says it can't access a particular package. I know the NIC driver is correct, because doing a manual install its the only driver the machine will select, and when booting to WinPE.....its the only driver that will allow the machine to boot to WinPE successfully and start running the image Task Sequence. What I can't figure out for the past week is why its happening. It doesn't make much sense, and its more than a bit frustrating that its failing right at the last bit, everything else appears fine . But then when I ignore the error message, and allow the machine to boot to Windows without finishing the TS, none of the drivers appear to be installed as it doesn' get an IP address, how does any of this make sense? I've attached the latest log from this morning's failed image if anyone can point what might resolve this. smsts-20140904-093003.log
  9. Hi guys, I think I am a bit further forward with this, but its a head scratcher. I believe the machine is losing its IP address settings near the very end of the imaging process. I pressed F8 when the error popped up on screen and did an ipconfig, the IP settings were blank/not present. When I did this ipconfig check at the beginning of the imaging process, the machine had a working IP address and was communicating fine. The only thing I can't figure out now is: Why would it be losing its IP settings? Surely when it installs the drivers in the Task Sequence, it should keep its settings? Especially if its using the NIC Driver that I put into the WinPE Boot Image? Has anyone ever experienced this before? Thanks for any and all input guys!!
  10. smsts-20140829-114621.logMorning guys its me again I'm still having difficulty trying to get one of our new model PC's imaging correctly with our SCCM system. The machine APPEARS on the surface to image ok, but then at the very end of the image process I get the (0x80070002) error mentioned above where the system fails at running part of the task sequence. I just re-imaged one of our older model PC's, and it images perfectly fine. In my eyes, this proves there is nothing wrong with the image/packages we have been using in the past. I pulled off the error logs for the PC I'm having trouble with, and it seems to be having difficulty accessing the MDT Files package that we have. There are a number of persistent occurrences in the log, with different second counts where it says the following: "Failed to connect to "\\SERVERNAME\SMSPKGD$\ABZ00005" (1231). Retry in 13 seconds. InstallSoftware 29/08/2014 11:43:01 2452 (0x0994)" Failed to connect to "\\SERVERNAME\SMSPKGD$\ABZ00005" (1231). Retry in 14 seconds. InstallSoftware 29/08/2014 11:43:14 2452 (0x0994) Another bit of the log then says the following: Failed to connect to the share \\SERVERNAME\SMSPKGD$\ABZ00005\ with default account InstallSoftware 29/08/2014 11:43:53 2452 (0x0994) Creating a connection to the share \\SERVERNAME\SMSPKGD$\ABZ00005\ with network access account InstallSoftware 29/08/2014 11:43:53 2452 (0x0994) What the logs don't really make clear is, WHY would the system have difficulty in accessing this particular package? The older model machines we have don't have any problems and image fine, so I'm rather stumped. I've attached the full log-file if anyone would like to have a look at it with SMS Trace or something and would like to look for the error code (0x80070002). Its interesting to note: When I image with an older PC, it also joins the PC to the network domain without any issues. With this Dell OptiPlex 7020, it doesn't put it on the domain, and the process finishes as a standalone machine without any of the drivers installed Can anyone offer any additional input please?
  11. Are the logs during an image deployment kept on the SCCM server somewhere? I have re-created the driver package, populated the drivers back into the driver store on the server and also used the import wizard to populate the corresponding driver package with the drivers. I have added the driver for the machine's model (OptiPlex 7020) to the boot image and updated the distribution point so it knows to use the right driver for this machine. I have tried to deploy an image to the machine, and it appears to be failing, I think, at the tail end of the deployment. The machine tries to boot up, but I get an error message "Task Sequence: Windows 7 Target deployment has failed with the error code (0x80070002)". When I click close, the machine boots up fine, but it is then not on my domain. Would this still be a driver issue? Can I find the logs for the failed deployment on the server or are they only kept on the machine during an image job?
  12. I do have an additional problem though. I created a new task sequence for installing the relevant drivers for a Dell OptiPlex PC. It completes the image process through WinPE, but then when the machine is trying to apply settings for first use, it fails with a message saying "windows could not configure one or more system components"........so it looks like at this rate, I'll need to remove the TS for installing the drivers, and just image the machine and install the drivers manually.
  13. Not having much luck. I've added in all the drivers to the boot image for this model machine, a Dell OptiPlex 7020. Tried booting to the NIC, but I get the same problem. It boots, gets to "preparing network settings" then the dialog box disappears, it stays on the SCCM splash screen about 30 secs and then reboots. And these are the drivers from Dell's own SCCM Cab file on their website! EDIT: I figured out where I was going wrong, a very rookie mistake. It helps to update the distribution point whenever you add driver(s) to a boot image. I hadn't updated the distribution point after adding in the driver so the system wasn't able to see the correct drivers.
  14. Hi Jorgen, thanks for replying. I notice that guide is for SCCM 2012, and I'm using 2007. When I right click on a driver package, I don't have a "show members" option that the guide specifies. How would I get around this? Thanks
  15. Hi guys, is there somewhere within SCCM that specifies what WinPE boot image is used in the imaging process?? We've just bought in some new PC's, and they're not booting into SCCM correctly. The machine boots over PXE, I get the SCCM 2007 Splash screen, but then instead of being able to select which OS to install and crack on, it stays on the SCCM Splash screen saying "preparing Windows settings" I think it says, that then disappears, and the machine reboots itself automatically after 30 secs or so. I'm thinking the WinPE boot image needs updating as the version on Dell's website for an OptiPlex 7020 is WinPE Version 3 and according to our SCCM system, its a customised version 1 that's being used, although I'm wondering how accurate that really is. :S. My question is, and I've never done this bit before so its all new, if I add in the new WinPE......how can I tell SCCM to use that in future deployments? Am I even looking in the right direction? Cheers guys! Sisko EDIT: I've just been reading up about WinPE on TechNet, and it says Configuration Manager 2007 requires WinPE Version 2.0, yet I just checked our system and I don't think we have any service packs for our SCCM. Under "Help, About" it simply says "System Centre Configuration Manager Version 4.00.6487.2000"......I suspect our SCCM is hideously out of date if I'm reading up about Service Packs 1 & 2 for SCCM 2007......so, does that mean that even if I download WinPE Version 3 from Dell's website, our System won't take it?
  • Create New...