Jump to content


dgriffin

Established Members
  • Posts

    8
  • Joined

  • Last visited

Everything posted by dgriffin

  1. Hello, I'm currently building out an environment for testing SCCM 2103 and ran into this error (see screenshot) at the beginning of the setup. I have the following in my environment: -Server 2022 -SQL 2019 -SCCM 2103 Everything is setup as I normally would with configuring SCCM but I can't figure out why I get this error. Any help is greatly appreciated.
  2. Hmmm... its not listed at that location on my vm. The only place I find a CCM or Log directory is under C:\Program Files. Both are seperate folders. The logs folder doesn't contain the file. This sucks.
  3. @almababy Where was the log located? Can't seem to find mine. Before upgrading to Sp1, I tried importing the vmware drivers and that didn't work either. I'll have to try again.
  4. One more thing, I don't know where the smtslog is located. There's a folder called logs under the SCCM folder on C: but it doesn't contain that file.
  5. I have all of the correct boundaries listed in SCCM, I also upgrade to SP1. Still does the same thing. If I could get this portion of SCCM working, all should be fine. Anyone have any other suggestions? Thanks alot for all of your comments!
  6. Hi, I've been searching all over for the location for the smtslog. Do you know where it is located?
  7. Hi All, My test lab is ran on VMware with 1 AD server and a memeber server with SCCM 2012, and SQL installed. Everything else within SCCM works fine but when it comes to deploying an OS, the task sequence fails. Here's the full error: Task Sequence Failed - An error occurred while retreiving policy of this computer. I've searched high and low for a fix but what I had tried doesn't work. Some suggest that the bios time/date is the issue, or pki certs are needed. Tried both methods with no success. Any input would be great. Thanks
×
×
  • 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.