Video Screencast Help

Asterisks not accepted as wildcard characters for computer name in Configuration Set

Created: 19 Mar 2013 • Updated: 20 Mar 2013 | 7 comments

In Windows Server 2012, when creating a New Configuration Set I get this error when using asterisks as wildcards for the computer name:

"You must specify a valid computer name, that does not contain any '*' characters"

Symantec's own configuration instructions say to use asterisks as wildcards, so I'm not sure why this error appears, unless it has to do with compatibility of my version of Ghost Console (11.5.0.2113) with the OS. Any help is appreciated. Thank you.

Operating Systems:

Comments 7 CommentsJump to latest comment

EdT's picture

I would recommend you use LiveUpdate to get your version updated to 11.5.1.2266.

If you still have a problem then come back and let us know.

If your issue has been solved, please use the "Mark as Solution" link on the most relevant thread.

MacBrinky's picture

Yes, as EdT is telling you, please perform an update of your Ghost Solution Suite installation.
Indeed a lot of issues have been fixed with the first service pack.
You should not have this issue under 11.5.0.2266.

EdT's picture

....or even under 11.5.1.2266 ??  <g>

If your issue has been solved, please use the "Mark as Solution" link on the most relevant thread.

kms0201's picture

Thanks for the suggestion. I did the update to 11.5.1.2266, but still get the error.

EdT's picture

Did you update the clients as well as the server? Both need to be done for consistent operation.

If your issue has been solved, please use the "Mark as Solution" link on the most relevant thread.

kms0201's picture

The sever isn't connected to any clients yet. I'm simply trying to configure a machine group that will generate unique computer names when I push the image.

EdT's picture

You have to bear in mind that Symantec's Ghost documentation is many years old, as the development team was laid off several years ago. Consequently, you have to allow for the changes in server operating systems that have taken place in the intervening years, which may make the documentation invalid.

If your issue has been solved, please use the "Mark as Solution" link on the most relevant thread.