I run a computer that functions as a server for transferring files into and out of the company. It runs Jscape MFT server. I've recently had to migrate over to a new domain and since doing so, the Server service on the computer goes through a continuous Start / Stop process.
Does anyone have any experience with this? Any suggestions on how to resolve this?
What information do you need for assistance?
Related
I'm currently trying to create a PowerShell script which is capable of automatically creating Hyper-V VMs, configuring them and installing a AD domain.
Infrastructure: the script is creating 3 VMs: 2x Server 2016 Core (meant for the DCs) and 1x Windows 10 Pro
After creating a new forest with Install-ADDSForest. DC1 will automatically reboot. Directly after that DC2 is trying to execute Install-ADDSDomainController which is failing because it can't contact the domain, because something on DC1 isn't ready.
I've already tried to wait for PowerShell Direct & gpsvc (because the shell is showing "Waiting for gpsvc" for a long time.). I've also tried to ping the domain name and execute Install-ADDSDomainController after ICMP reply.
Now to my question: What service needs to be running in order to add the other server as a DC?
I would then get the status of that service and continue my script if that named service is running.
I would also appreciate if someone could provide a different/better solution!
Thanks in advance.
Edit:
I've found somewhat of a solution for my case:
I'm now catching the error with try catch inside a do while loop.
I have 3 tier architecture server which are 1 Web Front Ender Server (WFE), 1 Application Server (APP) and 1 Database Server (DB) that installed in 1 physical server / host. Then suddenly the host broken caused by the RAM is broken.
After that happen, we done some recovery and use the VM backup then restore it to the new host / physical server. After we restored all the Virtual Machine (WFE, APP, DB) the sharepoint running OK and then when we try to retract and deploy some solutions, the deployment status stucks at deploying and retracting whenever we tried.
We have tried to deploy and retract from Central Administration, using powershell command, and using stsadm command line but keeps getting the same result. Anyone having the same problem ? and how you solve this ?
After I tried many things to fix the problem.
Finally I fixed the problem. All I did,
1.Checking the Sharepoint Timer Service running on every Sharepoint Server in farm
2.Restarting the Sharepoint Timer Service (you can check the service in windows services.msc) on every Sharepoint Server (Web Front End Server and Application Server) in the farm at the same time
Thank you guys
Problem: System Center Endpoint Protection keeps deploying itself from SCCM to the computers and servers after I manually delete them, even if the SCCM server got completely removed recently. Though AFAIK the deployment tasks weren't deleted, only the services stopped and SCCM related programs uninstalled. Also the server (Hostname: SCCM_SERVER) was shutdown.
If I open one of the servers and go to Configuration Manager, I see that Assigned management point is still SCCM_SERVER.
Question: Not having been delved into SCCM administration prior, how is this happening? Did it create windows services on each machine? Could there be additional SCCM administration sever running somewhere else? I checked GPO/scheduled tasks - nothing. How does the deployment work? And how do I stop it?
Also, if additional information related to the software/hardware/network is required please ask.
Regards,
Sai
Have you checked the log file EndpointProtectionAgent.log? Maybe it can give us some clues.
If you want to decommission SCCM, you could uninstall the SCCM client.
The correct way is edit the Client Settings node in the Administration workspace first.
Modify the device settings "Install Endpoint Protection client on client computers", choosing False or No will not uninstall the Endpoint Protection client. To uninstall the Endpoint Protection client, set the Manage Endpoint Protection client on client computers client setting to False or No. Then, deploy a package and program to uninstall the Endpoint Protection client.
#About client settings in System Center Configuration Manager
In SAP HANA index server and statistics server stopped suddenly and not running.
I tried to stop and restart the server by the following commands.
HDB stop
HDB start
But still it is not working. Does anyone know what causes this problem and what is the solution? Thanks in advance.
If the indexserver doesn't start, you cannot logon as SYSTEM (or any other user for that matter). A good way to find out what the reason for the failed start is to check the tracefile for the nameserver, the indexserver and the statisticsserver.
Logon as <sid>adm and change to the tracefile folder via cdtrace.
Then find the tracefiles and use e.g. less to read through them to find the actual error messages.
Alternatively you can use SAP HANA Studio with the emergency connection to review the trace files without terminal access.
We are having a massive system having around 15 servers hosting .Net WCF services, mvc application etc.
When we do a deployment (out of office hours) we have to uninstall and install everything on the live servers.
This takes lot of time and if something goes wrong we have to rollback everything.
can you please suggest something different to this?
like
Deply into a other environment (whenever you like) and switch the URL to point to new servers
[This comes with the overhead of cost of maintaining 2 copies of production (active and passive)]
any other ideas please.
Does services need to be uninstalled for all deployments ?
You can have a script that does this against all the servers in parallel:
Stop any windows services
Stop IIS
Make backup of replaced files
XCopy assemblies, resources, website files.
Perhaps run InstallUtil if deploying a service (as needed).
Start IIS and services.
Such a script will not take too long to execute. With 15 servers it will be well worth the effort writing it and make the deployment and rollback process completely automated.
It sounds like you need a load balancer to handle the trafic to your production servers. You would deploy all your new code to Server Farm B and test it using a test DNS entry. Once you are satisfied with the changes you would repoint your load balancer addresses from Server Farm A to Server Farm B it will then become live. The only down side to this is with database changes.