HI All,
I want to add Cal License in RDS server which is already installed and configured.
Please let me know how to add cal license and activate it.
↧
Remote Desktop service ( I want to add Cal License in RDS server which is already installed and configured)
↧
Server Manager/Powershell Taskbar Icon Removal Server 2012
After scanning for two days for a Group Policy setting that allows me to unpin these two icons from my users taskbar and browsing the support threads both here and abroad, I am at a loss as to how to do this through group policy on my terminal server.
Situation: I have disabled Server manager from running but the icon continues to be present on the taskbar for all of my users on the terminal server.
Mission: Find a way to remove the two icons using group policy.
Execution: Task 1: Find Filesystem in GP. Many suggestions have you add to the Local Computer Policy>Computer Configuration>Policies>Windows Settings>Security Settings>File System section in gpedit.msc. This setting is simply not there. I have found it in Local Computer Policy>Computer Configuration>Administrative Templates>System>Filesystem.
Task 2: Add files to Filesystem.
%AllUsersProfile%\Microsoft\Windows\Start Menu\Programs\Accessories\Windows PowerShell\Windows PowerShell.lnk
%AllUsersProfile%\Microsoft\Windows\Start Menu\Programs\Accessories\Windows PowerShell\Windows PowerShell (x86).lnk
%AllUsersProfile%\Microsoft\Windows\Start Menu\Programs\Administrative Tools\Server Manager.lnk
%AllUsersProfile%\Microsoft\Windows\Start Menu\Programs\Administrative Tools\Windows PowerShell Modules.lnk
In the right click menu you do not have the option to add anything to this section.
Question: If we are not able to add these files to the Filesystem section, how do we turn off the icons? Is there a better way that does not involve a script? Should the GPO be created from the DC?
↧
↧
Server Manager Performance Counters Won't Start on Single Server
Good morning, everyone.
I have a Windows Server 2012 R2 Data Center I am using to setup a central administration point for all of our Windows servers. I have one Windows Server 2008 R2 server that does not want to comply. Every other server simply required an install of the following items.
- Microsoft .NET Framework 4.0 (In our case 4.5.2)
- Windows Remote Management 3.0 (Afterwards reboot, login, go to cmd Run-As Administrator: winrm quickconfig)
No matter what I get the following error.
"The Server Manager Performance Monitor collector could not be disabled. Error: -2147023838"
I cannot find anything regarding this error and how to resolve it. I can't track the error back to its point of origination.
Any help would be wildly appreciated!
↧
Need to obtain missing packages in CheckSUR.log
I cannot access "Turn Windows features on or off" (blank window). CheckSUR.log shows:
Unavailable repair files:
servicing\packages\Package_1_for_KB2952664~31bf3856ad364e35~amd64~~6.1.16.5.mum
servicing\packages\Package_1_for_KB3035583~31bf3856ad364e35~amd64~~6.1.3.2.mum
servicing\packages\Package_3_for_KB2952664~31bf3856ad364e35~amd64~~6.1.16.5.mum
servicing\packages\Package_for_KB2952664_SP1~31bf3856ad364e35~amd64~~6.1.16.5.mum
servicing\packages\Package_for_KB2952664~31bf3856ad364e35~amd64~~6.1.16.5.mum
servicing\packages\Package_for_KB3035583_RTM~31bf3856ad364e35~amd64~~6.1.3.2.mum
servicing\packages\Package_for_KB3035583~31bf3856ad364e35~amd64~~6.1.3.2.mum
servicing\packages\Package_1_for_KB2952664~31bf3856ad364e35~amd64~~6.1.16.5.cat
servicing\packages\Package_1_for_KB3035583~31bf3856ad364e35~amd64~~6.1.3.2.cat
servicing\packages\Package_3_for_KB2952664~31bf3856ad364e35~amd64~~6.1.16.5.cat
servicing\packages\Package_for_KB2952664_SP1~31bf3856ad364e35~amd64~~6.1.16.5.cat
servicing\packages\Package_for_KB2952664~31bf3856ad364e35~amd64~~6.1.16.5.cat
servicing\packages\Package_for_KB3035583_RTM~31bf3856ad364e35~amd64~~6.1.3.2.cat
servicing\packages\Package_for_KB3035583~31bf3856ad364e35~amd64~~6.1.3.2.cat
My PC has KB2952664/6.1.17.2.295 and KB3035583/6.1.3.2.3035 installed. I can't delete the obsolete/erroneous Registry enties. Unistalling KB2952664 and KB3035583, SFC, and CHKDSK do not solve the problem.
Where can I get the above missing packages?
↧
MSN page open automatically while opening IE
HI
we have win-2008 r2 as Dc
group policy set for all clients to open default homepages -http://myportal.domain.co.in,http://capital.domain.co.in
when we open iE from client system three pages are coming (msn page,http://myportal.domain.co.in,http://capital.domain.co.in)
but we set two pages only, automatically msn page coming,
i cant understand why msn page popup while open IE
Please can anyone help me
Regards
Surendhar.J
↧
↧
Windows server 2012 R2 Domain Controller failing to log into itself
Never had this issue on the server for the few years its been running, i was in a situation where the local account password was needed to be reset. I reset the password then instantly started getting failed logins.
I tracked down a few of the failed logins...services....active directory...windows credentials. But i am unable to find this last one!
Yes this server is fully patched!
Spent alot of time crawling the internet trying to find this issue, i am unable to find anything!
Here is a snippet of the log:
___________________
An account failed to log on.
Subject:
Security ID:
SYSTEM
Account Name:
AAC-DC1$
Account Domain:AAC
Logon ID:
0x3E7
Logon Type:3
Account For Which Logon Failed:
Security ID:
NULL SID
Account Name:
Account Domain:
Failure Information:
Failure Reason:Unknown user name or bad password.
Status:
0xC000006D
Sub Status:
0xC0000064
Process Information:
Caller Process ID:0x2b8
Caller Process Name:C:\Windows\System32\lsass.exe
Network Information:
Workstation Name:AAC-DC1
Source Network Address:-
Source Port:
-
Detailed Authentication Information:
Logon Process:Schannel
Authentication Package:Kerberos
Transited Services:-
Package Name (NTLM only):-
Key Length:
0
This event is generated when a logon request fails. It is generated on the computer where access was attempted.
The Subject fields indicate the account on the local system which requested the logon. This is most commonly a service such as the Server service, or a local process such as Winlogon.exe or Services.exe.
The Logon Type field indicates the kind of logon that was requested. The most common types are 2 (interactive) and 3 (network).
The Process Information fields indicate which account and process on the system requested the logon.
The Network Information fields indicate where a remote logon request originated. Workstation name is not always available and may be left blank in some cases.
The authentication information fields provide detailed information about this specific logon request.
- Transited services indicate which intermediate services have participated in this logon request.
- Package name indicates which sub-protocol was used among the NTLM protocols.
- Key length indicates the length of the generated session key. This will be 0 if no session key was requested.
________________________
↧
An attempt was made to reference a token that does not exist: Server Manager
I am getting an error when trying to open up the Server Manager on Windows 2008 Server R2.
"Microsoft Management Console:
An attempt was made to reference a token that does not exist."
I know that the cause of this error is due to my use of a registry cleaning program called Wise Registry Cleaner. Even though I had made a backup of my registry before using this program and cleaning my attempts at a restore from the backup have failed. I have come to the MS Technet Fourms in hopes that I can resolve this and any other related issues without resorting to a format. Any advice on fixing this problem will be much appreciated.
Edit:
This error also happens for Windows Server Backup. It probably happens for other things too.
↧
Cannot Install WINS on Server 2008 R2
Hey Everyone!
Hope you are all well! I have an issue that I'm hoping someone can shed some light on. I'm trying to install WINS on a 2008 R2 HP server and I get an error saying the installation failed. When I checked the servermanager log file the following is there:
5000: 2011-03-24 13:06:57.942 [CBS] IsCacheStillGood: True.
5000: 2011-03-24 13:06:58.270 [ServerManagerCmd] Start Installation...
5000: 2011-03-24 13:06:58.301 [Sync]
Sync Graph of changed nodes
==========
---------------------------------------------------------------------------
name : WINS Server
state : Changed
rank : 1
sync tech: CBS
ant. : empty
pred. : empty
provider : Provider
5000: 2011-03-24 13:06:58.301 [Sync] Calling sync provider of WINS Server ...
5000: 2011-03-24 13:06:58.301 [Provider] Sync:: guest: 'WINS Server', guest deleted?: False
5000: 2011-03-24 13:06:58.301 [Provider] Begin installation of 'WINS Server'...
5000: 2011-03-24 13:06:58.301 [Provider] Install: Guest: 'WINS Server', updateElement: 'WINSRuntime'
5000: 2011-03-24 13:06:58.317 [Provider] Installation queued for 'WINS Server'.
5000: 2011-03-24 13:06:58.348 [CBS] installing 'WINSRuntime ' ...
5000: 2011-03-24 13:06:58.786 [CBS] ...parents that will be auto-installed: '<none>'
5000: 2011-03-24 13:06:58.786 [CBS] ...default children to turn-off: '<none>'
5000: 2011-03-24 13:06:58.801 [CBS] ...current state of 'WINSRuntime': p: Staged, a: Staged, s: UninstallRequested
5000: 2011-03-24 13:06:58.817 [CBS] ...setting state of 'WINSRuntime' to 'InstallRequested'
5000: 2011-03-24 13:06:58.833 [CBS] ...'WINSRuntime' : applicability: Applicable
5000: 2011-03-24 13:06:59.676 [CbsUIHandler] Initiate:
5000: 2011-03-24 13:09:28.409 [CbsUIHandler] Error: -2147021879 :
5000: 2011-03-24 13:09:28.409 [CbsUIHandler] Terminate:
5000: 2011-03-24 13:09:28.549 [CBS] ...done installing 'WINSRuntime '. Status: -2147021879 (80070bc9)
5000: 2011-03-24 13:09:28.565 [Provider] Skipped configuration of 'WINS Server' because install operation failed.
5000: 2011-03-24 13:09:28.565 [Provider]
[STAT] ---- CBS Session Consolidation -----
[STAT] For
'WINS Server'[STAT] installation(s) took '150.2094462' second(s) total.
[STAT] Configuration(s) took '0.0035154' second(s) total.
[STAT] Total time: '150.2129616' second(s).
5000: 2011-03-24 13:09:28.565 [Provider] Error (Id=0) Sync Result - Success: False, RebootRequired: True, Id: 40
5000: 2011-03-24 13:09:28.580 [Provider] Error (Id=0) Sync Message - OperationKind: Install, MessageType: Error, MessageCode: -2147021879, Message: <null>, AdditionalMessage: The requested operation failed. A system reboot is required to roll back changes
made
5000: 2011-03-24 13:09:28.612 [ServerManagerCmd] Error (Id=0) Installation of [WINS Server] WINS Server failed. The server needs to be restarted to undo the changes.
5000: 2011-03-24 13:09:28.627 [ServerManagerCmd] [STAT] Overall Sync Time: '150.3272195' second(s)
5000: 2011-03-24 13:09:28.627 [ServerManagerCmd] Error: Installation of one or more roles, role services, or features failed, and a restart is required. Check the Server Manager log for additional information
and try again.
I've tried running through the System Update Readiness Tool, but when I check the logs in "%SYSTEMROOT%\Logs\CBS\CheckSUR.log" and "%SYSTEMROOT%\Logs\CBS\CheckSUR.persist.log" they both say "No errors detected". This is on a brand new HP server with a fresh install of Server 2008 R2. So far this has been the only feature I can't seem to install because I've installed Telnet Client, SNMP Service, etc fine. I've checked the event logs on the server as well, but nothing unusual other than that the installation of WINS failed.
Any help with this would be VERY much appreciated! Thanks so much in advance for any ideas!
Cheers
↧
Problems adding a GVLK license to a KMS server
Hi,
My KMS server is running and handing out licenses for Windows 7 Enterprise but I need to add a key for Office 2013. I ran the Office 2013 volume license setup pack. Then I added what should have been my KMS key according to the Licensing Center. When I run slmgr /dlv I get a message, which I can't post here at the moment, which seems to be a combination of the Server license and the CSVLK of my volume license key that I could get to install. I can't get the setup key to authenticate. I've tried slmgr /upk <auth ID> to remove the CSVLK and start over but with no luck.
Any help would be greatly appreciated.
↧
↧
Server Manager Error 0x800F080D Roles & Features Server 2008 R2
I recently had all kinds of problems with my Server 2008 R2 and file corruption. I've pretty much repaired everything but Server Manager. I am getting error 0x800F080D when I try and view Roles or Features.
Here is my output from the System Update Readiness Tool
Summary:
Seconds executed: 3227
Found 117 errors
CSI Manifest Missing Total count: 72
CSI Manifest Failed Catalog Check Total count: 3
CSI Payload File Missing Total count: 33
CBS MUM Missing Total count: 5
CBS MUM Corrupt Total count: 2
CBS Catalog Missing Total count: 1
CBS Catalog Corrupt Total count: 1
Unavailable repair files:
winsxs\manifests\amd64_microsoft-windows-security-ntlm_31bf3856ad364e35_6.1.7601.23153_none_db3618059269850f.manifest
winsxs\manifests\wow64_microsoft-windows-rpc-local_31bf3856ad364e35_6.1.7601.23153_none_1cd2749ba953d351.manifest
winsxs\manifests\amd64_microsoft-windows-security-kerberos_31bf3856ad364e35_6.1.7601.23153_none_455a085de0ac51ef.manifest
winsxs\manifests\amd64_microsoft-windows-ie-ieetwcollector_31bf3856ad364e35_11.2.9600.18097_none_a5a0063017ae1bc8.manifest
winsxs\manifests\amd64_microsoft-windows-cryptsvc-dll_31bf3856ad364e35_6.1.7601.18839_none_d414ef57b17a9fd5.manifest
winsxs\manifests\x86_microsoft-windows-msmpeg2adec_31bf3856ad364e35_6.1.7601.19091_none_938805c115ddab0d.manifest
winsxs\manifests\x86_microsoft-windows-cryptbase_31bf3856ad364e35_6.1.7601.19110_none_676909140c3fe98a.manifest
winsxs\manifests\amd64_microsoft-windows-security-schannel_31bf3856ad364e35_6.1.7601.23126_none_80bce6e2850690ea.manifest
winsxs\manifests\msil_system.deployment.resources_b03f5f7f11d50a3a_6.1.7601.23230_en-us_ba23423724babe45.manifest
winsxs\manifests\x86_microsoft-windows-msmpeg2enc_31bf3856ad364e35_6.1.7601.19091_none_0aeb4c05a4862408.manifest
winsxs\manifests\amd64_microsoft-windows-ie-datawarehouse_31bf3856ad364e35_11.2.9600.18097_none_2937a6401552d7f0.manifest
winsxs\manifests\amd64_microsoft-windows-ie-f12tools.resources_31bf3856ad364e35_11.2.9600.18097_en-us_8d325583c9d86d0c.manifest
winsxs\manifests\amd64_d8f6363c280654b063b170a3462955d3_31bf3856ad364e35_6.1.7601.19050_none_1369e66b836e2558.manifest
winsxs\manifests\amd64_29bb8aa44ae60d5fb13a8361deb002e4_31bf3856ad364e35_6.1.7601.19073_none_0088288394a15f59.manifest
winsxs\manifests\amd64_microsoft-windows-smss_31bf3856ad364e35_6.1.7601.18923_none_0a54ce062fda3ad2.manifest
winsxs\manifests\amd64_microsoft-windows-smb10-minirdr_31bf3856ad364e35_6.1.7601.18923_none_e6beb1926217489d.manifest
winsxs\manifests\amd64_microsoft-windows-smbminirdr_31bf3856ad364e35_6.1.7601.18923_none_ddab933e67c60a3b.manifest
winsxs\manifests\amd64_microsoft-windows-security-schannel_31bf3856ad364e35_6.1.7601.18923_none_803071176beb71d9.manifest
winsxs\manifests\amd64_microsoft-windows-kernel32_31bf3856ad364e35_6.1.7601.18923_none_f1d80b4a6cf423c6.manifest
winsxs\manifests\amd64_microsoft-windows-security-ntlm_31bf3856ad364e35_6.1.7601.18923_none_dacd12dc79335e30.manifest
winsxs\manifests\wow64_microsoft-windows-rpc-local_31bf3856ad364e35_6.1.7601.18923_none_1c696f72901dac72.manifest
winsxs\manifests\amd64_microsoft-windows-smb20-minirdr_31bf3856ad364e35_6.1.7601.18923_none_e8f51ba4a06e7c0e.manifest
winsxs\manifests\wow64_microsoft-windows-lsa_31bf3856ad364e35_6.1.7601.18923_none_0eb95b1da7d49549.manifest
winsxs\manifests\amd64_microsoft-windows-security-kerberos_31bf3856ad364e35_6.1.7601.18923_none_44f10334c7762b10.manifest
winsxs\manifests\amd64_microsoft-windows-kernelbase_31bf3856ad364e35_6.1.7601.18923_none_851c9e5ccb3cabb2.manifest
winsxs\manifests\wow64_microsoft-windows-security-kerberos_31bf3856ad364e35_6.1.7601.18923_none_4f45ad86fbd6ed0b.manifest
winsxs\manifests\amd64_microsoft-windows-ie-adminkitbranding_31bf3856ad364e35_11.2.9600.18097_none_56d9dbd16c64869d.manifest
winsxs\manifests\amd64_microsoft-windows-ie-antiphishfilter_31bf3856ad364e35_11.2.9600.18097_none_de1b85af80a5e029.manifest
winsxs\manifests\amd64_microsoft-windows-ie-ieproxy_31bf3856ad364e35_11.2.9600.18097_none_72b853b75f77f055.manifest
winsxs\manifests\amd64_microsoft-windows-security-schannel_31bf3856ad364e35_6.1.7601.23153_none_80997640852198b8.manifest
winsxs\manifests\amd64_4cf5186ff0d1d2425accc08f0266fc17_31bf3856ad364e35_6.1.7601.23255_none_729779f5069f564d.manifest
winsxs\manifests\amd64_26c8aa1670c1ab294211e43dbba3f410_31bf3856ad364e35_6.1.7601.23278_none_8f796e4efd88c7a0.manifest
winsxs\manifests\x86_microsoft-windows-c..tionauthorityclient_31bf3856ad364e35_6.1.7601.23313_none_da0d88a6b4086371.manifest
winsxs\manifests\x86_microsoft-windows-msmpeg2adec_31bf3856ad364e35_6.1.7601.23290_none_9410a4282efc2ea7.manifest
winsxs\manifests\x86_microsoft-windows-i..rolviewer.resources_31bf3856ad364e35_11.2.9600.18163_en-us_28d1770f1932465e.manifest
winsxs\manifests\amd64_microsoft-windows-ie-jsprofilerui_31bf3856ad364e35_11.2.9600.18097_none_d58868ffe31a4b7d.manifest
winsxs\manifests\x86_microsoft-windows-cryptbase_31bf3856ad364e35_6.1.7601.23313_none_67f5a8a3255ad280.manifest
winsxs\manifests\wow64_microsoft-windows-security-kerberos_31bf3856ad364e35_6.1.7601.23126_none_4fd2235214f20c1c.manifest
winsxs\manifests\amd64_microsoft-windows-smb10-minirdr_31bf3856ad364e35_6.1.7601.23126_none_e74b275d7b3267ae.manifest
winsxs\manifests\amd64_microsoft-windows-smbminirdr_31bf3856ad364e35_6.1.7601.23126_none_de38090980e1294c.manifest
winsxs\manifests\amd64_microsoft-windows-kernel32_31bf3856ad364e35_6.1.7601.23126_none_f2648115860f42d7.manifest
winsxs\manifests\amd64_microsoft-windows-security-ntlm_31bf3856ad364e35_6.1.7601.23126_none_db5988a7924e7d41.manifest
winsxs\manifests\wow64_microsoft-windows-rpc-local_31bf3856ad364e35_6.1.7601.23126_none_1cf5e53da938cb83.manifest
winsxs\manifests\amd64_microsoft-windows-security-digest_31bf3856ad364e35_6.1.7601.23126_none_9973e6ebac78cdf2.manifest
winsxs\manifests\amd64_microsoft-windows-smb20-minirdr_31bf3856ad364e35_6.1.7601.23126_none_e981916fb9899b1f.manifest
winsxs\manifests\wow64_microsoft-windows-lsa_31bf3856ad364e35_6.1.7601.23126_none_0f45d0e8c0efb45a.manifest
winsxs\manifests\amd64_microsoft-windows-security-credssp_31bf3856ad364e35_6.1.7601.23126_none_225ecd43d153befa.manifest
winsxs\manifests\amd64_microsoft-windows-security-kerberos_31bf3856ad364e35_6.1.7601.23126_none_457d78ffe0914a21.manifest
winsxs\manifests\amd64_microsoft-windows-kernelbase_31bf3856ad364e35_6.1.7601.23126_none_85a91427e457cac3.manifest
winsxs\manifests\amd64_microsoft-windows-ie-htmlrenderingmedia_31bf3856ad364e35_11.2.9600.18097_none_a10a1a7e6e335a58.manifest
winsxs\manifests\amd64_microsoft-windows-ie-f12resources_31bf3856ad364e35_11.2.9600.18097_none_64f4db71221e65a1.manifest
winsxs\manifests\amd64_microsoft-windows-ie-memoryanalyzer_31bf3856ad364e35_11.2.9600.18097_none_a580877a0878cafe.manifest
winsxs\manifests\amd64_8f2d6bf40257f37f5932b22ad754cd14_31bf3856ad364e35_6.1.7601.23255_none_3769b912820b926f.manifest
winsxs\manifests\amd64_a7fc99a15050eb90eaa2db8d18160888_31bf3856ad364e35_6.1.7601.19050_none_3761499fb2605b4f.manifest
winsxs\manifests\amd64_microsoft-windows-s..-jscript9.resources_31bf3856ad364e35_11.2.9600.18097_en-us_c4449d138cf7e46b.manifest
winsxs\manifests\amd64_5a342c815329b65c9c5321b9946d78d5_31bf3856ad364e35_6.1.7601.18834_none_9f13b57032fbefe5.manifest
winsxs\manifests\amd64_microsoft-windows-b..os-loader.resources_31bf3856ad364e35_6.1.7601.23153_en-us_d51be53813e2986a.manifest
winsxs\manifests\amd64_microsoft-windows-ie-ielowutil_31bf3856ad364e35_11.2.9600.18097_none_e8ff7b7e86220e1b.manifest
winsxs\manifests\amd64_microsoft-windows-scripting-jscript_31bf3856ad364e35_11.2.9600.18097_none_656957ef0c0baafd.manifest
winsxs\manifests\amd64_8d01b1e70b51719c08f902e133a0ff54_31bf3856ad364e35_6.1.7601.19050_none_d7b87a308fcadee0.manifest
winsxs\manifests\amd64_microsoft-windows-ocspsvc.resources_31bf3856ad364e35_6.1.7601.23223_en-us_b375e712e5a92ba3.manifest
winsxs\manifests\amd64_229da53ff8c1e3e4513589903547860a_31bf3856ad364e35_6.1.7601.19050_none_fe09c1c1f2a733b0.manifest
winsxs\manifests\amd64_microsoft-windows-ie-f12_31bf3856ad364e35_11.2.9600.18097_none_d03daa96fd4a3202.manifest
winsxs\manifests\wow64_microsoft-windows-ntdll_31bf3856ad364e35_6.1.7601.18923_none_c145ae9d47370929.manifest
winsxs\manifests\wow64_microsoft-windows-kernel32_31bf3856ad364e35_6.1.7601.18923_none_fc2cb59ca154e5c1.manifest
winsxs\manifests\wow64_microsoft-windows-security-digest_31bf3856ad364e35_6.1.7601.18923_none_a33c1b72c7be70dc.manifest
winsxs\manifests\wow64_microsoft-windows-kernelbase_31bf3856ad364e35_6.1.7601.18923_none_8f7148aeff9d6dad.manifest
winsxs\manifests\amd64_microsoft-windows-security-ntlm_31bf3856ad364e35_6.1.7601.18869_none_daa7d302794e68d7.manifest
winsxs\manifests\amd64_microsoft-windows-ie-lowreg_31bf3856ad364e35_11.2.9600.18097_none_8ad5a159f8c83693.manifest
winsxs\manifests\amd64_ae04139537e98713d3cb21359081efb3_31bf3856ad364e35_6.1.7601.23255_none_1ed472371963243b.manifest
winsxs\manifests\amd64_microsoft-windows-scripting-vbscript_31bf3856ad364e35_10.2.9200.21299_none_af8cb3b7b7e4287e.manifest
winsxs\manifests\wow64_microsoft-windows-kernelbase_31bf3856ad364e35_6.1.7601.23126_none_8ffdbe7a18b88cbe.manifest
winsxs\manifests\wow64_microsoft-windows-ntdll_31bf3856ad364e35_6.1.7601.23126_none_c1d224686052283a.manifest
winsxs\manifests\wow64_microsoft-windows-security-ntlm_31bf3856ad364e35_6.1.7601.23126_none_e5ae32f9c6af3f3c.manifest
winsxs\manifests\wow64_microsoft-windows-security-digest_31bf3856ad364e35_6.1.7601.23126_none_a3c8913de0d98fed.manifest
servicing\packages\Package_2_for_KB3097877~31bf3856ad364e35~amd64~~6.1.1.2.mum
servicing\packages\Package_41_for_KB3102429~31bf3856ad364e35~amd64~~6.1.1.0.mum
servicing\packages\Package_41_for_KB3102429~31bf3856ad364e35~amd64~~6.1.1.0.mum
servicing\packages\Package_for_KB3102429~31bf3856ad364e35~amd64~~6.1.1.0.mum
servicing\packages\Package_2_for_KB3108664~31bf3856ad364e35~amd64~~6.1.1.0.mum
servicing\packages\Package_for_KB3092601_SP1~31bf3856ad364e35~amd64~~6.1.1.0.mum
servicing\packages\Package_for_KB3097877_SP1~31bf3856ad364e35~amd64~~6.1.1.2.mum
servicing\packages\Package_for_KB3108664_SP1~31bf3856ad364e35~amd64~~6.1.1.0.mum
servicing\packages\Package_for_KB3108664~31bf3856ad364e35~amd64~~6.1.1.0.mum
servicing\packages\Package_2_for_KB3097877~31bf3856ad364e35~amd64~~6.1.1.2.cat
servicing\packages\Package_41_for_KB3102429~31bf3856ad364e35~amd64~~6.1.1.0.cat
servicing\packages\Package_41_for_KB3102429~31bf3856ad364e35~amd64~~6.1.1.0.cat
servicing\packages\Package_for_KB3102429~31bf3856ad364e35~amd64~~6.1.1.0.cat
servicing\packages\Package_2_for_KB3108664~31bf3856ad364e35~amd64~~6.1.1.0.cat
servicing\packages\Package_for_KB3092601_SP1~31bf3856ad364e35~amd64~~6.1.1.0.cat
servicing\packages\Package_for_KB3097877_SP1~31bf3856ad364e35~amd64~~6.1.1.2.cat
servicing\packages\Package_for_KB3108664_SP1~31bf3856ad364e35~amd64~~6.1.1.0.cat
servicing\packages\Package_for_KB3108664~31bf3856ad364e35~amd64~~6.1.1.0.cat
Any help would be appreciated.
↧
CBS.persist.log - Can Delete?
On my windows 2008 servers CBS.log and alot CBS.persist.log consume alot of disk space. some forum / article mention CBS.persist.log are safe to delete but some article not recommence to remove it. Can the CBS.persist.log be deleted? any risk?
↧
Sharing and permission on windows server 2008
I have 40 clients and 1 server ( Windows Server 2008)
On the server, I created 40 folders corresponds to 40 clients.
I don't upgrade DC. How to 1 client only can access 1 folder
EX: First Client can access one folder and can't access other folders
↧
Scheduled task won't run .bat file
Hi. On Windows Server 2008 I have a scheduled task that calls a .bat file. The fist step in the .bat file is write to a log file to the same directory in which the .bat file exists. This allows me to find out if it is ever run. When the .bat file is run from a command prompt it runs as expected writing to the log file and completing its actions. My problem is that when I run the scheduled task manually or allow it to run when scheduled it appears to run but the .bat file is never run. No log file is ever created. The History tab in the properties of the scheduled tasks shows the task being started and running then completing with an operation code of 2. I've disabled the UAC for the user account. I've set the task to run as the Administrator user and verified the permissions for that user. I know the password is correct for the task because I can make changes to the properties and save those changes with the username/password. I'm at a loss for further troubleshooting steps. Can anyone point me in the right direction to figure out why these .bat files are not being run?
↧
↧
Server manager won't start
This is a Windows 2008 R2 server with all updates installed. It is a virtual server and it has been working for several years and this problem started around 4/7/2016.
I receive the following error message. Name Server Manager CLSID: FX: {18ea3f92-d6aa-41d9-a205-20234008cfbb}.
I've tried NETFrame repair Tool.
Uninstalled and RE installed NET Framework
Except I'm not able to uninstall or reinstall NetFramework 2.xxxx because I need to initiate "Turn Windows Features On and Off" in Programs and Features and I'm not able to initiate "Turn Windows Features On and Off" I receive the Server Manager error above.
I've been able run MMC and add computer management but not all the functions are available. For example Even Manager errors with a slightly different error message. Name: Even Viewer CLSID: FX: {b05566ae-fe9c-4363-be057-7a4cbb7cb510}
I'm also not able to add Task scheduler snap-in. Name: Task Scheduler CLSID: FX: {c7b8fb06-bfe1-4c2e-9217-a69a95bbac4}
I'd appreciate any suggestions.
↧
VxCJMon.dat
A mysterious file named VxCJMon.dat is appearing on many servers, most on the root of "c" others found on file shares. So far I am unable to find any information concerning this file - does anyone know what this file is?
↧
MMC /32 not working in Windows 10?
We are able to add available snap-in using MMC command in Run. When we tried to use MMC /32 command in Run, we are not able to add available snap-in. It says mmc has stopped working. In Event Receiver I can see the following error
Fault bucket 107747373301, type 1
Event Name: APPCRASH
Response: Not available
Cab Id: 0
Problem signature:
P1: mmc.exe
P2: 10.0.10586.0
P3: 5632d419
P4: SqlManager.dll_unloaded
P5: 2011.110.2100.60
P6: 4f35e2c3
P7: c0000005
P8: 0002d833
P9:
P10:
Attached files:
C:\Users\shailesh\AppData\Local\Temp\WER5862.tmp.WERInternalMetadata.xml
These files may be available here:
C:\ProgramData\Microsoft\Windows\WER\ReportArchive\AppCrash_mmc.exe_91fef55887df38ac829fecfe5c416e95e314aa8_3b70ea27_1d6b800e
Analysis symbol:
Rechecking for solution: 0
Report Id: 75dcc229-a112-4914-8026-95007f814382
Report Status: 0
Hashed bucket: 3a03c58a0537cf61aad7cb6ce8704ee0
Please provide solution
↧
how to add dropbox to windows 2012 vps server
how to add dropbox to windows 2012 vps server which was downloaded from amazon.com
↧
↧
Online - "Access Denied" error when using domain admin account to manage as
I did a fresh install of server core 2012 R2 datacenter, joined it to the domain and then went to manage it from a windows 8 machine running server manager.
I added the new server to server manager, used the "manage as" to connect with a domain user who is a member of the domain admin group and it still said "Online - Access Denied".
I had to add my domain user (domain admin) to the local administrators group of the server core install to get around this.
I don't understand why this is? When I pulled the list of local administrators on the server core install it had domain administrators listed as a local administrator, so why didn't my domain admin work until I added the user manually?
Thanks for any insight
↧
Connectivity tools apart from RDP
One of our supported customer is looking for remote connectivity tool to connect server apart from RDP.
Can you please share some details of the remote connectivity tool which can be used and also comment on the licensing cost
↧
Enable/Disable new connections in Server Manager with a script
Hello,
Yesterday I was looking through the host servers within the Remote Desktop Servers Collection and saw that one of the RD server was not allowing new connections to be made.
Now I am wondering if it is possible to allow new connections with a script (PowerShell or CMD)?
Note: I added a picture for reference
↧