Deployment Architecture

Citrix Target Server Image from Master Golden Image

apple75
New Member

We are utilizing a deployment server to push out UF agent config to our Citrix VM, however, not all devices are reporting into Deployment server---they are showing in Splunk cloud as all devices sending data

 

In working with support they suggested to rename  /opt/splunkforwarder/etc/instance.cfg to backup_instances.cfg (or something similar)

This seems to work for the device to register, however, this will be overwritten when a new master image push out is done

Has anyone encountered this before and what steps have you used to monitor devices on DS

Thanks,

Jeff

My engineering team uses the following script for Splunk config

Seal Script

# generalize splunk

Stop-Process -InputObject $p -Force

Start-Sleep -Seconds 3

if (get-service -Name SplunkForwarder | Where status -eq "stopped")

    {

        write-host "Splunk Service Stopped..."

    }

$Host.PrivateData.VerboseForegroundColor = 'Yellow'

start-process -nonewwindow -filepath "C:\Program Files\SplunkUniversalForwarder\bin\splunk.exe" -argumentlist 'clone-prep-clear-config' -wait -verbose

write-host "Splunk Machine ID removed..."

Labels (1)
0 Karma
Got questions? Get answers!

Join the Splunk Community Slack to learn, troubleshoot, and make connections with fellow Splunk practitioners in real time!

Meet up IRL or virtually!

Join Splunk User Groups to connect and learn in-person by region or remotely by topic or industry.

Get Updates on the Splunk Community!

ATTENTION: We’re Moving! (AGAIN!)

The Splunk Community Slack is undergoing a system migration to keep our workspace secure and ...

Deep Dive: Optimizing Telemetry Pipelines in Splunk Observability Cloud

In this session, we will peel back the layers of Splunk Observability Cloud’s cost-optimization features. ...

Announcing Modern Navigation: A New Era of Splunk User Experience

We are excited to introduce the Modern Navigation feature in the Splunk Platform, available to both cloud and ...