Provisioning Issues: Migration of Physical K1000 to VM w/ new Hostname
Good afternoon ninjas,
Our production environment is currently a physical k1000 on our public internet. We are configuring a virtual machine on our vlan, and starting from scratch without importing data from our production server. It's possibly compromised, so we're starting fresh to avoid the same issue.
We'll call my environments:
K1Production.mysite.com (Current production)
K1VM.mysite.com (New build)
My current infrastructure checks into my production environment and reports inventory. I would like these devices to start checking into my VM.
Currently, I can use my production K1 to push out a script which updates the hostname on the existing amp.conf file for my Windows PCs, successfully.
However, what I'd like to do, if possible, is simply leverage the provisioning capability in the VM to just start from scratch, so to speak, and get a fresh inventory.
However, on a machine that has no agent, I get this result from attempted provisioning:
I also so perhaps I could re-provision from my VM to a machine that already has an established connection with my production server, perhaps just overwriting the amp.conf, but no dice with that either.
Any ideas on an easier method to re-provision? Sure my scripts works to update amp.conf, but if provisioning as a whole is not working, that doesn't help me for new deployments.
Our production environment is currently a physical k1000 on our public internet. We are configuring a virtual machine on our vlan, and starting from scratch without importing data from our production server. It's possibly compromised, so we're starting fresh to avoid the same issue.
We'll call my environments:
K1Production.mysite.com (Current production)
K1VM.mysite.com (New build)
My current infrastructure checks into my production environment and reports inventory. I would like these devices to start checking into my VM.
Currently, I can use my production K1 to push out a script which updates the hostname on the existing amp.conf file for my Windows PCs, successfully.
However, what I'd like to do, if possible, is simply leverage the provisioning capability in the VM to just start from scratch, so to speak, and get a fresh inventory.
However, on a machine that has no agent, I get this result from attempted provisioning:
| [01/12/17 03:12:54 PM] Begin provisioning... [01/12/17 03:12:54 PM] Executing Windows platform provisioning. STEP 1: CONNECT TCP/SSH - SUCCESSFUL [01/12/17 03:12:56 PM] Executing remote communications: Initializing RPC Connecting to ADMIN$ Copying service file Disconnecting ADMIN$ Connecting to IPC$ STEP 2: AUTHENTICATION - SUCCESSFUL Opening pipe to service IN: pipe_open(\KBRemoteService, 7098287) Sending commands Commands: //K1VM.mysite.com/client/agent_provisioning/windows_platform/agent_msi_provision.bat K1VM.mysite.com client ampagent-6.4.522-x86.msi K1VM.mysite.com Sending login credentials Login: Domain\AdminAcct process (//K1VM.mysite.com/client/agent_provisioning/windows_platform/agent_msi_provision.batK1VM.mysite.com client ampagent-6.4.522-x86.msi K1VM.mysite.com) could not be launched: 64 The specified network name is no longer available. (authenticated, but CreateProcessAsUser failed)process (//K1VM.mysite.com/client/agent_provisioning/windows_platform/agent_msi_provision.bat K1VM.mysite.com client ampagent-6.4.522-x86.msi K1VM.mysite.com) could not be launched as LocalSystem: 64 The specified network name is no longer available. OpenService - NT_STATUS_OK StopService - NT_STATUS_OK DeleteService - NT_STATUS_OK CloseServiceHandle - NT_STATUS_OK CloseSCMHandle - NT_STATUS_OK Connecting to ADMIN$ Deleting service file Disconnecting ADMIN$ STEP 3: PUSH SCRIPT\PROVISIONING - FAILED [01/12/17 03:12:56 PM] End of remote communications. [01/12/17 03:12:56 PM] End provisioning run. |
Any ideas on an easier method to re-provision? Sure my scripts works to update amp.conf, but if provisioning as a whole is not working, that doesn't help me for new deployments.
1 Comment
[ + ] Show comment
Answers (0)
Please log in to answer
Be the first to answer this question
It looks like there's a communication issue with the K1 and those clients. Do you know if the clients are able to ping the K1000 by hostname or if it can go to the client share and pull the files that way? - KACE_Irwin 7 years ago