Jump to content


fr43nk

error 0x00000032

Recommended Posts

Hi all.

 

When i run the task sequence (attached as tasksequence.png),

i get at the second step, where it should read the networksettings, an

error 0x00000032.

This error means "not supported".

My smsts.log shows no error. (attached as smsts.log)

 

Since I host 2 domains, each hosted by its own sccm2012 server, i am confused, cause

the same task sequence runs fine in the other domain.

 

Can you give me a hint, where I can start looking for a misconfiguration?

smsts.log

post-16302-0-54226200-1354636361_thumb.png

Share this post


Link to post
Share on other sites

Can I ask then Why are you capturing network settings if you have DHCP on your network?

 

I thought this task component was to help customers that have no DHCP running on the network(maybe im wrong) so it will capture static assigned IP addresses on hosts so that when deployment is finished there is no need to manually assign the statics again!

Share this post


Link to post
Share on other sites

SCCM will hold onto the hostname without this and as for the domain ......specify it in the TS network settings should be enough, if not just attach an answerfile to the TS with domain settings in it!!

 

Do not think you need to capture/read network settings for what you are trying to achieve!!

 

 

As to why it works on 1 domain & not the other....did you export the TS from one to another??

 

Rocket

Share this post


Link to post
Share on other sites

When I disable "migrate networkcardconfiguration" and only leave "migrate domain and workgroupmembership" (@ capture networksettings),

I get the error 0x00000032 without any hint in smsts.log too.

 

What really drives me mad, is that its not showing up in the smsts.log....

Share this post


Link to post
Share on other sites

It seems that I need to capture it, because if I disable the step "capture networksettings",

the client beomes a new AD-Client with a hostname like "minint-xxxx

 

This should not happen...if SCCM has a record of the host in the DB then it should not rename it to something different......this would only happen if the target machine is unknown to SCCM, then it will give it a generic MININT-XXXXX name..(but this could be overcome by using variables or a script so that OSD time and the computer is unknown, it will request you to enter in a new name)

 

By any chance are you deleting the accounts from SCCM first and then using unknown PXE boot on them??

 

To which collection are you deploying your TS to?

 

Are you running your TS out to the live OS and not using PXE?

Share this post


Link to post
Share on other sites

i dont delete the sccm record of the client first.

I am deploying this TS to a test collection, the client is because of a name query in the right collection.

This TS only works, if a client is in this collection, unknown machines wont get it - for unknown machines exists a

seperate TS, which works fine.

 

The TS is run using PXE, cause I dont want that the TS is visable in the softwarecenter. To achieve that, I configured in the TS options, that

it only can be run on Vista SP2, cause we dont have this OS in our company.

But that cant be the issue, cause i do it the same way in the other domain.

Share this post


Link to post
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.

Guest
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

Loading...


×
×
  • 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.