unable to determine architecture of \\Tony (80070005h) tbnetmanage

[badamsiosllc]

I was running the app on a computer in my dining room, and successfully installed both the client and IFW to my computer in my garage. I then said to myself, I said, self, that's kinda dumb, because I spend most of my time in the garage, and was using tightvnc to work on it from remote.

Since I have a PC and server 2022 domain controller in the garage (here:) I installed it on the server. (Incidentally, the Domain name is SOPRANO

I get the same error on Junior here, and A.J. in the kitchen.

I then get this error: Connection to service manager on \\either failed 5.

A.J. is a member of the domain, Junior is not.

Also, both have a question mark under network neighborhood. I'm assuming that's because the clients are not installed.

[TeraByte Support]

5 is access denied, you'll need to use a domain admin (presuming all systems on joined to the domain), otherwise for workgroups, you have to setup user accounts on the multiple systems. See manual / help for details on permissions settings.

[badamsiosllc]

Okay, thanks.

Seems I forgot to tell this to notify me of replies.

[badamsiosllc]

Hey, this just keeps getting stranger and stranger. I setup a virtual network of 3 win 11 pc's all in the same workgroup. I disabled the firewalls on each, so remote management service should not be an issue, nor should WMI. UAC is disabled on them as well and file sharing is enabled. I created shares on them all and they can access all shares. I did however, set the users that can access the shares to everyone.

I don't see anything about user names and passwords under non-domain client systems in the help. And, just for giggles and grins, I removed any and all software relating to terabyte on the domain controller, and it installed it!

I even went so far as to manually install the client service on each virtual machine, it told me it was successfully installed and started.

[badamsiosllc]

Actually, upon reading other reading, I found this:

For systems not in a domain (such as a home network), you need to have an administrator account on the system (create one, if necessary) and save the credentials for it on the system running TBNetManage.

I don't understand what that means. I see no place in tbnetmanage to save any credentials.

And you know what's really sad? I was a network engineer until 15 years ago. Now I'm just plain old.

[OldNavyGuy]

save the credentials for it on the system running TBNetManage.

[badamsiosllc]

Yeah, that's what I don't understand. Does that mean to create the accounts on the tbnetmanager "server"?

I'll give that a shot, then, thanks.

But why does a non-domain pc able to install it on a DC?

And thanks for your patients.

[TeraByte Support(PP)]

On the remote system you would need to have an administrator account that you can access. For example, if there is already one on it (you, the normal user, etc.) and you have the login credentials, you can use that. Otherwise, you need to create a new admin account on that system (new user with admin privileges).

For saving credentials on the system running TBNetManage, you would use the Credential Manager app (in the Windows Control Panel or can search the Start menu) and add them as Windows Credentials or Generic Credentials (one may work better than the other).