Jump to content


tmiller_hockey

Established Members
 View Profile  See their activity

  • Posts

    139

  • Joined

  • Last visited

 Content Type 

Everything posted by tmiller_hockey

  1. tmiller_hockey
    I'd seriously consider making all the AD/Domain moves first. SCCM isn't impossible to install, the pre-reqs are fairly well laid out. Have you tried using the unified installer?
  2. tmiller_hockey
    Does anyone know an easy way to remove Altiris agents from our current machines in bulk? There is a command running a .exe with a switch that does this but what would be an easy way to deploy this with SCCM?
  3. tmiller_hockey
    Figured out the answer myself. I created a TS last week that used the x64 boot image. This seems to have made the WDS use the x64 for everything. I changed that particular TS to use the x86 boot image and all is well.
  4. tmiller_hockey
    All of a sudden when booting PXE, it is now downloading the x64 boot image instead of the x86 as it was before. I'm trying to figure out why as some of our machines don't support x64 and fail to boot PXE. Has anyone heard of this or have any idea? Our imaging process is practically stopped because of this and since school is starting in two weeks.....definitely not a good thing, LOL Thanks, Todd
  5. tmiller_hockey
    I am now getting this error when trying to capture Win 7 x64 using Capture Media. Before I was receiving an 0x800704CF error and found an post on the forums that mentioned it and said it was a write permissions issue with where the image is going to be stored even though it was a domain admin account with full control. The suggestion was to capture to an external drive. I tried this and now am receiving the 0x80004005 error. I'll try to post my smsts.log
  6. tmiller_hockey
    Thanks Rocket Man, this would work great for good notice ahead of time but we are probably only going to get about 15 minutes notice before the power goes out. I contacted Dan Ireland who wrote the SCCM Right Click tools and he is going to look into adding that ability into the Right Click tools.
  7. tmiller_hockey
    Mine seems to have cleared up on its own but still don't know why it was happening. The amount of imaging we were doing has dropped off some but most of the time, we are imaging about 50-60 clients at a time.
  8. tmiller_hockey
    Does anyone have a way this can be done easily? Due to rolling blackouts that are coming, we need the ability to shut these machines down ahead of time. My thought was a script package deployed to a collection but if there were some machines already off, when they start back up they'd get shut down. Really need to figure something out with this, my execs are being relentless.
  9. tmiller_hockey
    Has anyone successfully deployed this with SCCM? I'm using 2012. I've found various cryptic ways they say it can be done but none of them seem to work. Thanks!!
  10. tmiller_hockey
    Has anyone else experienced this? Event Logs only showing it terminated unexpectedly.
  11. tmiller_hockey
    I'd love to see something like this as well!
  12. tmiller_hockey
    I've just been informed that we will need the capability to power off machines in collections due to the probable rolling power blackouts that we experience here. Is this possible easily or will I need to install the Out Of Band Management point?
  13. tmiller_hockey
    Here is my issue. Our image was built with a MAK key for Office 2010. Since I didn't build the images, I payed no attention to this. Well after imaging over 1000 machines, we've figured out that we need to use a KMS host for Office activation as our MAK keys are running over. I've already installed the Office KMS host on a machine that currently activates our Server 2008 R2 boxes, the problem is how to change all the machines that have been imaged that won't activate over to the KMS host so they will activate. I know we will need to redo the image to input the KMS key but how can I change what's already out there? Thanks!
  14. tmiller_hockey
    I have one machine that is giving us fits. No matter what we do, the machine won't image. When booting to PXE and after entering the PXE password it says that no Task Sequences are available for this computer. All my image jobs are deployed to All Systems and All Unknown Computers and every other machine works fine. Anyone seen this or have any ideas?
  15. tmiller_hockey
    My higher ups ask the same questions. One thing you might look at is client activity and last login times in the properties of the users device. At least that gives you some sort of idea of when the user was utilizing their devices.
  16. tmiller_hockey
    Try looking at the partitioning setup in the Task Sequence. Set it to 100% of disk. We had some machines doing this and that fixed it for us.
  17. tmiller_hockey
    So can someone explain how you would create an ADR that would automatically populate weekly and deploy to a Windows 7 machine collection?
  18. tmiller_hockey
    Our problem was solved using the iphelper in our switches.
  19. tmiller_hockey
    So isn't SCCM supposed to do that for you in the client settings?
  20. tmiller_hockey
    That means it should work as a batch file I can create on the Flash Drive, yay!
  21. tmiller_hockey
    Is Group Policy controlling your updates?
  22. tmiller_hockey
    I'm in sort of the same scenario, I have 13 different campus locations and want to create another DP. Question is, should I enable PXE on that DP or not? I'd be putting the DP in one of the campuses that's furthest away from our Data Center. BTW we have a 10Gb link between here and that campus.
  23. tmiller_hockey
    I ran into some issues since mine was on a different box but looks my thought train was going down the wrong tracks
  24. tmiller_hockey
    Is your Distribution Point on a different box?
  25. tmiller_hockey
    Does everything look fine in your SUP status and component status?
×
×
  • Create New...

Important Information

We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue.