I have an AppAssure core that had a few protected machines that were removed, but the recovery points were kept.
How do I get those formerly protected machines' recovery points moved to a different AppAssure core? Or, how do I archive them to reclaim the space they're eating up?
One of my servers was rebooted recently and CHKDSK was run. When I run a DFS Diagnostic report on it, the DFS environment shows the server that was rebooted is now in a state of "Auto Recovery". However, it's been in that state for over 48 hrs now. I understand it can take some time, since the folders in the replication group have thousands of files, and they're relatively large, but 48 hrs seems pretty long.
I've read several articles about DFS start up after a "dirty" shutdown, but there are no Error 2213 or 2004 in my servers.
Also, this key: HKLM\SYSTEM\CurrentControlSet\Services\DFSR\Parameters\StopReplicationOnAutoRecovery was already set to 0
Is there a way I can see what's going on?
Is there a way I can improve performance on the Auto Recovery state?
Is there a way for me to determine if the Auto Recovery state is doing anything?
I have a printer that exists as \\printserver01\printer
For whatever reason, when I publish/add it to AD, part of the name gets cut off. For example, it becomes \\printserver0\printer
When users go to search for the printer through the Devices and Printers option on their desktop, it lists just fine as "printer on printserver01", but if you do a search in AD for the printer, you'll see the server name is listed as "printserver0" instead of "printserver01". I tried using FQDN, but the issue still remains with the last character being chopped off.
Has anyone come across this before? How can this be resolved?
I adopted a HyperV environment and I'm trying to squeeze every bit of performance I can get out of it.
Some of the virtual machines in the environment have IDE drives instead of SCSI drives.
Is it safe to mount the VHDx as a SCSI drive? Or do I need to convert it?
My alternative is to add a SCSI drive, boot up into knoppix, DD the IDE drive to the SCSI drive, then unmount the IDE drive.
I'm trying to mount a Windows cifs share (shared by Windows) onto a CentOS box, per user. Users are all in Active Directory.
So, every user who logs into their Linux box should be mounting the drive with their own credentials.
A solution I found was to mount using:
mount -t cifs //servername/mylogin /home/mylogin/windows -o uid=mylogin -o gid=groupname -o credentials=/home/mylogin/winpasswd
And for the /home/mylogin/winpasswd:
username=mylogin
domain=domainname
password=password_in_plain_text
However, I don't want to manually implement this for every Linux box and every user on every Linux box. Also, I don't want users having their password in plain text anywhere. Is there a way to mount a Windows cifs share and bypass the password prompt without a password file?
I adopted a virtual Windows Server 2012 Storage Server that has 4 QNAPs attached via iSCSI.
The storage environment is connected via iSCSI through a Cisco SG300 (Gigabit); jumbo frames is not configured.
Each QNAP is individually configured as a RAID 6 with 8 drives each unit.
(2) of the QNAPs are configured in the Storage Server as a MIRROR via Disk Management
(2) of the QNAPs are configured in the Storage Server as a MIRROR via File and Storage Services using Storage Pools
For whatever reason, the QNAP mirror via Disk Management works as expected and the QNAP mirror via Storage Services performs poorly.
Bandwidth wise, I'm expecting around 60-100MB/s, but I'm averaging 30MB/s. I do get a spike every now and again around 80MB/s, but I also get long bouts of no throughput whatsoever. It's not consistent.
CPU utilization is under 5% and memory is steady at 21%.
Is this discrepancy in my expectation due to the Storage Server mirroring process or is this expected of RAID6 in general? I'm running perfmon now to collect data, but it seems odd that there'd be such poor and inconsistent performance.
UPDATE:
PS C:\Windows\system32> fsutil fsinfo ntfsinfo d:
NTFS Volume Serial Number : 0xb0fe9f7ffe9f3c92
NTFS Version : 3.1
LFS Version : 2.0
Number Sectors : 0x000000077ffbefff
Total Clusters : 0x00000000efff7dff
Free Clusters : 0x000000009991ea4a
Total Reserved : 0x0000000000000000
Bytes Per Sector : 512
Bytes Per Physical Sector : 4096
Bytes Per Cluster : 4096
Bytes Per FileRecord Segment : 1024
Clusters Per FileRecord Segment : 0
Mft Valid Data Length : 0x0000000000040000
Mft Start Lcn : 0x00000000000c0000
Mft2 Start Lcn : 0x0000000000000002
Mft Zone Start : 0x00000000000c0040
Mft Zone End : 0x00000000000cc840
Resource Manager Identifier : F19B79FA-AFE8-11E5-80C0-3CA82A1CECDB
PS C:\Windows\system32> fsutil fsinfo ntfsinfo f:
NTFS Volume Serial Number : 0xa832ab9d32ab6f4e
NTFS Version : 3.1
LFS Version : 2.0
Number Sectors : 0x0000000ffffbefff
Total Clusters : 0x00000000ffffbeff
Free Clusters : 0x0000000095e4dba5
Total Reserved : 0x0000000000000000
Bytes Per Sector : 512
Bytes Per Physical Sector : 512
Bytes Per Cluster : 8192
Bytes Per FileRecord Segment : 1024
Clusters Per FileRecord Segment : 0
Mft Valid Data Length : 0x0000000000040000
Mft Start Lcn : 0x0000000000060000
Mft2 Start Lcn : 0x0000000000000001
Mft Zone Start : 0x0000000000060000
Mft Zone End : 0x0000000000066420
Resource Manager Identifier : E628C5C7-CA70-11E5-80C5-3CA82A1CECDB
I'm using Exchange 2003 SP2 (I know, I need to upgrade this, but there are bureaucratic issues that need to be worked out first) and am having difficulties with the Free/Busy Schedule. For some reason, it's defaulted to publishing only 2 months of Free/Busy info for users, even though my GPO has it set for 6 months, and my non-policy registry key is set for 6 months.
These are my non-policy registry keys:
[HKCU\Software\Microsoft\Office\14.0\Outlook\preferences\fbpublishrange] = 6
[HKCU\Software\Microsoft\Office\14.0\Outlook\preferences\fbupdatesecs] = 900
Note: this setting wasn't configured on one of my users' computers, so I added it, and it seemed to resolve the issue yesterday, but the view reverted to 2 months this morning, even though the setting persists.
These are my policy registry keys:
[HKCU\Software\Policies\Microsoft\office\14.0\outlook\preferences\fbpublishrange] = 6
[HKCU\Software\Policies\Microsoft\office\14.0\outlook\preferences\fbupdatesecs] = 900
The policy is managed by GPO and is being applied properly to my computer/user profile:
My exchange environment is made up of 4 back-end servers and 1 front-end server. I'm explicitly managing all public folders (including the free-busy schedule) on 1 back-end server (meaning I have no mailboxes on this folder; I built it specifically for public folders to resolve an issue I was having with public folder replications). All mailbox stores are configured by system policy to default to the 1 back-end server I designated for public folders.
I'm lead to believe this is a public folder issue, but I can't see how, since only 1 server is serving public folders, and there aren't any special permissions needed for the Free/Busy schedule.
Why would my free/busy schedule only publish 2 months of info when I have it configured for 6? This is happening for all my users.
I adopted a quirky environment. One of my DFS servers is a Windows Server 2003 Standard R2 server with:
The (5) virtual drives are set up as a dynamic disk. I want to consolidate them into (1) virtual disk.
I have considered using dd_rescue by adding another virtual disk in the size that I need, then doing a bit-by-bit copy of my E drive, but I'm concerned it may have adverse effects on my DFS cache if the new drive doesn't take the E drive letter upon boot-up after I move the partitions. I'm also not sure if dd_rescue has any issues working with dynamic disks.
I've also considered doing a V-to-V, but that process could take a while to complete with 1.8TB of data total.
Is there a way I can consolidate the (5) virtual drives without the risk of corrupting my DFS? If so, how do I consolidate multiple virtual disks attached to a VM guest? (I'm running VMware vCenter/vSphere ESXi 5.5)
I have a question similar to this. However, I have a problem with my Exchange 2003/Outlook 2010 environment where some users future availability doesn't show, while others do.
My Outlook is set up to publish 2 months of Free/Busy. This is configured in GPO. However, as you can see from the image, 12/1/2014 is not 2 months away from today (10/21/2014) and yet, the schedule is unavailable for one of the users. I have other examples of this for multiple users, and it seems to be random.
I have multiple Exchange 2003 back-end servers and one Exchange 2003 front-end server. All my public folders are located in one back-end server, specifically created just for public folders and the free/busy system folder. Some users are on different servers, while others are on the same servers. The users who I can't see future availability for is consistent for other users as well.
Has anyone come across a problem like this? What would make the free/busy calendar show for some users, but not others, for anything over 8 weeks?
UPDATE
If I open the user's calendar to view, it shows me the free/busy calendar. This issue only comes up if I go to schedule using the scheduling view.
I have 4 back-end servers and 1 front-end server in an Exchange 2003 array. I'm having tons of replication issues, because there's just way too much data in the public folders (or so I suspect). Some of the folders are getting upwards to 5GB in size, and some public folders have upwards of 20 subfolders.
Each back-end server holds users for a different office location.
Currently, if someone on server1 sends something to the public folder, it can take 1s-45min for it to replicate to any of the other servers, but anyone else on server1 see's it right away.
I've tried limiting the folder replication to just one server to remove replication all together, in hopes that all the servers would just point to the server with the public folder, but it doesn't seem to work that way.
Does having a public folder on one server in an Exchange 2003 array populate it for users on another server? Is there a more elegant option?
My SSL certificate is for *.example.com but my internal domain is junk.com. I have an Exchange environment that masquerades as mail.example.com.
This was working from what I could tell for the last year, until I noticed an issue with the Intermediate Certificate Authority, where the certificate installed in IIS6 for the Default Web Server couldn't verify the certificate.
To resolve this, I redownloaded my certificate from my vendor and installed the Intermediate Certificate Authority and SSL certificate. After restarting IIS, people trying to access Outlook Web Access were being met with ERR_SSL_PROTOCOL_ERROR. I put a work around in place by using a self-signed certificate, but this brings up that "do not trust this certificate" warning. People can continue on to the portal after acknowledging the warning, but that causes confusion for users.
Was I mistaken about how this works? Are you supposed to be able to use an SSL certificate assigned for *.example.com onto a different domain like junk.com where the Exchange environment is masquerading as the certificate's domain? If so, how do I get it to work properly?
I adopted a junk Exchange 2003 environment. I need to consolidate the (2) administrative groups into (1). I've moved over the Public Folders in the top-level, but I need to clean up the replication.
Currently, the public folders are replicating to servers in the old administrative group, new administrative group, or both. I am manually changing the replication settings for each public folder and their sub-folders, but this is time consuming. I looked in the System Policies, and I cannot configure anything to set what servers will hold the replications. Is there another way I can do this other than manually for all folders and sub-folders?
I adopted an environment that is having an issue with email routing where emails are delayed due to too many hops. Some of my users are able to send/receive with no delivery delays, but many of my users are experiencing send/receive delays both internally and externally.
All my email comes through a hosted spam filter, then it's forwarded to us.
Our environment has two Administrative Groups, CurrentGroup and OldGroup. These accept emails for multiple domains. All our emails are supposed to come through OldGroup, which has our smart-host (I'm assuming the previous IT team was trying to migrate from one to the other, but never finished the project).
OldGroup is connected to CurrentGroup using a Routing Group connector with the following servers as remote bridgeheads:
OldGroup has two SMTP connectors. The 1st SMTP connector goes to remote.partner.com (which is hosted in a different facility); all mail going here is forwarded through the partner's smarthost via public IP, with the local bridgehead SMART-HOST. The 2nd SMTP connector is supposed to route all out-going email using DNS with the local bridgehead SMART-HOST.
CurrentGroup is also connected to OldGroup with a Routing Group connector, with the remote bridgehead SMART-HOST. I made this change last night and it seemed to help, but I'm still having delivery problems.
CurrentGroup has one SMTP connector forwarding all mail through the smarthost SMART-HOST with the following local bridgeheads:
Here is a logical view:
Here is an example of my Exchange System Manager View:
On the Default SMTP Virtual Server service for all the servers, I've set up the smart-host value to be SMART-HOST.
I believe the problem lies somewhere between the Routing Groups. I'm not sure these are properly configured. Do I need an SMTP Connector from my CurrentGroup pointing to my OldGroup through SMART-HOST? and from OldGroup to CurrentGroup through the backend servers? How do I configure and verify my mail is routing between two Administrative Groups in Exchange 2003?
I adopted a junk environment, and I'm trying to stabilize it before I can migrate it to something better. My Exchange environment consists of
These servers are on Windows Server 2003 R2 SP2.
For some reason, the front-end server has a DNS server role on it. This is causing problems with Active-Sync since the DNS server is randomly taking ports, and sometimes takes the Active-Sync port. I already have an Active Directory server with the DNS role. Is a Microsoft Exchange 2003 Front-End Server required to be a DNS server?
In an effort to upgrade my environment, I added 2 new AD servers. When I shutdown my old AD servers, my Citrix environment (MetaFrame XPe for Windows version 1.0 SP1) stopped authenticating users. I've turned on my old AD servers, but my Citrix environment still won't authenticate.
I've generated a local account on the Citrix servers and confirmed I can authenticate with with on my ICA Client, but it won't authenticate my domain credentials. How do I view and change what server(s) my Citrix environment is using to authenticate myself and my users?
Desktop IP: 10.65.115.145
Server IP: 10.65.107.100
Local Core Switch: 10.65.0.1
Remote Core Switch: 10.64.0.1
Remote Server vLAN (sits in core switch): 10.64.30.1
Remote Server: 10.64.30.10
I tested this from another system on the same vlan as my desktop and found I am unable to ping or tracert from the desktop's vlan; this is weird, since I can tracert all the way up to the remote core switch.
Does this mean the issue is on the remote end? or is this an issue on the local end?
I'm trying to connect (2) Cisco Catalyst 2950's over each's respective FastEthernet 0/1 ports, but for some reason, they're not communicating. I'm doing this to physically extend my network and add more network ports.
On SwitchA (10.10.10.1) I have:
!
interface Porth-Channel1
description UPLINK
switchport mode trunk
switchport nonegotiate
flowcontrol send off
end
!
interface FastEthernet0/1
description ETHERNET-UPLINK
switchport mode trunk
channel-group 1 mode active
end
On SwitchB (10.10.10.2) I have:
!
interface Porth-Channel1
description UPLINK
switchport mode trunk
switchport nonegotiate
flowcontrol send off
end
!
interface FastEthernet0/1
description ETHERNET-UPLINK
switchport mode trunk
channel-group 1 mode active
end
I have the same config set up on an 8-port 2960 (SwitchC), and if I plug FastEthernet 0/1 of SwitchC to SwitchB or SwitchA, it works. But if I plug FastEthernet 0/1 of SwitchB to SwitchA, it doesn't work.
Am I missing something? How do I get it so I can connect 2 Cisco 2950 switches together?
On SwitchA:
#show int port-channel 1 trunk
Port Mode Encapsulation Status Native vlan
Po1 on 802.1q trunking 1
Port Vlans allowed on trunk
Po1 1-4094
Port Vlans allowed and active in management domain
Po1 1-2,5,30,112,115,120
Port Vlans in spanning tree forwarding state and not pruned
Po1 1-2,5,30,112,115,120
On SwitchB:
#show int port-channel 1 trunk
Port Mode Encapsulation Status Native vlan
Po1 on 802.1q trunking 1
Port Vlans allowed on trunk
Po1 none
Port Vlans allowed and active in management domain
Po1 none
Port Vlans in spanning tree forwarding state and not pruned
Po1 none
For SwitchB, I've tried to add all vlans to be allowed, but it doesn't change anything:
#config t
#int port-channel 1
#switchport trunk allowed vlan all
I've also tried:
#switchport trunk allowed vlan 1-4094
But the allowed vlan's doesn't change to what I tell it to. How do I fix this?
I ran a show int po1 switchport on both switches:
#show int po1 switchport
Name: Po1
Switchport: Enabled
Administrative Mode: trunk
Operational Mode: trunk
Administrative Trunking Encapsulation: dot1q
Operational Trunking Encapsulation: dot1q
Negotiation of Trunking: Off
Access Mode VLAN: 1 (default)
Trunking Native Mode VLAN: 1 (default)
Voice VLAN: none
Administrative private-vlan host-association: none
Administrative private-vlan mapping: none
Administrative private-vlan trunk native VLAN: none
Administrative private-vlan trunk encapsulation: dot1q
Administrative private-vlan trunk normal VLANs: none
Administrative private-vlan trunk private VLANs: none
Operational private-vlan: none
Trunking VLANs Enabled: ALL
Pruning VLANs Enabled: 2-1001
Protected: false
Appliance trust: none
#show int po1 switchport
Name: Po1
Switchport: Enabled
Administrative Mode: trunk
Operational Mode: down
Administrative Trunking Encapsulation: dot1q
Negotiation of Trunking: Off
Access Mode VLAN: 1 (default)
Trunking Native Mode VLAN: 1 (default)
Voice VLAN: none
Administrative private-vlan host-association: none
Administrative private-vlan mapping: none
Administrative private-vlan trunk native VLAN: none
Administrative private-vlan trunk encapsulation: dot1q
Administrative private-vlan trunk normal VLANs: none
Administrative private-vlan trunk private VLANs: none
Operational private-vlan: none
Trunking VLANs Enabled: ALL
Pruning VLANs Enabled: 2-1001
Protected: false
Appliance trust: none
Still no clue as to why show int po1 trunk shows Vlans allowed on trunk: none
I've been fiddling around with AIX 5.3.7 for hours today, and I was able to build a VG and LV, but I'm having difficulty using all the space in the LUN I carved out (500GB). I'm not sure if i'm running the right commands.
I have the LUN mapped from the SAN to the AIX box as hdisk16
I have the PV activated:
chdev -l hdisk16 -a pv=yes
I have the VG created:
mkvg -y logBUVG01 -s64 hdisk16
I have an LV created:
mklv -c1 -t jfs2 -y fslv01 logBUVG01 1
I go to format it:
crfs -v jfs2 -A yes -g logBUVG01 -m /fslv01 -a size=500G
But it fails saying I don't have enough free partitions. I don't understand how AIX determines space from the number of logical partitions or PP size, etc. If someone could clear this up for me, it would be great. How do I build my volume group/logical volume to utilize all the space I've carved out of my LUN?
I inherited an IBM System Storage DS4000 SAN with an AIX environment running Oracle RAC (3 nodes). One of the nodes crashed, so I got the system up and running with 2 nodes; however, the node that crashed was the node that was managing the backups. The backups were stored on a LUN in the SAN.
Due to the lack of documentation, I can see how they're mapped from /etc/filesystems, but I'm not sure how the AIX environment mapped these LUNs at bootup (other than the mapping association from the SAN management interface). I want to re-map the LUNs used for backups from the old node to one of the remaining nodes, but I'm concerned about losing the data on the LUNs.
I found some instructions here, but that seems like it's only for new LUNs. If I re-map the LUN to a new host, would the existing data on that LUN stay intact?
It looks like I knew less than I thought.
I created a new array on my storage controller called test and a new LUN called logbackup to test my theory and mapped it to one of the nodes as LUN 12.
On that node, when I ran cfgmgr, I ran into an error and followed these instructions to resolve it.
With cfgmgr working, I thought I'd be able to see the LUN, but I don't--or at least, the output of lspv, lscfg and lsdev -Cc Disk don't give me the information I can easily translate.
I've unmapped it and remapped the LUN a few times, but there is no change to the list of hdisks when I run cfgmgr.
Looks like I was reading my lscfg output incorrectly. I changed the LUN from 12 to 255 and saw a change in the lscfg. It mapped the LUN to hdisk16 so I added it as a physical volume using chdev -l hdisk16 -a pv=yes. Then, running fget_config -Av, I was able to confirm the LUN mapped properly. Now, it's just a matter of mounting it, writing to it, then migrating it to my other node to see if the data stays intact.
This is in regards to working on machines before joining the machine to a domain and although I would love to rely on GPO, that isn't an option at this time.
In the environment I'm working in, the firewall policy is to use a 3rd party Firewall app from an Total Endpoint Solution, so I have to disable the default Windows Firewall top prevent conflicts. I do this using a script that I run at the end of an imagine process or manually on systems I haven't reimaged. For a while, I was able to manage this using:
netsh advfirewall set allprofiles state off
However, that stopped working for some reason. So, I found I needed to clear the local security policy (manually):
Local Security Policy MSC > Windows Firewall with Advanced Security
Right-Click Windows Firewall with Advanced Security - Local Group Policy Object
Clear Policy
This was the script I used to avoid doing it manually:
secedit /configure /db reset /cfg securityprofile
A combination of both steps was working for about a month, then, for no apparent reason, it stopped working.
I began testing a registry hack to achieve what I needed, and it is giving me mixed results. I have two sets keys with profiles I need to change; for Local Profiles:
[HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\WindowsFirewall]
[HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\WindowsFirewall\DomainProfile]
"EnableFirewall"=dword:00000000
[HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\WindowsFirewall\PrivateProfile]
"EnableFirewall"=dword:00000000
[HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\WindowsFirewall\PublicProfile]
"EnableFirewall"=dword:00000000
For Domain Profiles:
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\services\SharedAccess\Parameters\FirewallPolicy]
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\services\SharedAccess\Parameters\FirewallPolicy\DomainProfile]
"EnableFirewall"=dword:00000000
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\services\SharedAccess\Parameters\FirewallPolicy\PublicProfile]
"EnableFirewall"=dword:00000000
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\services\SharedAccess\Parameters\FirewallPolicy\StandardProfile]
"EnableFirewall"=dword:00000000
The problem I'm having is that the Local Profile keeps regenerating the original settings with the firewall on. I've tried:
Result on old machine used for testing) good to go
a) Apply Local Policy Registry Hack
Result on old machine used for testing) good to go
a) use secedit to clear Local Security Policy
Result on old machine used for testing) good to go
a) use secedit to clear Local Security Policy
My goal is to disable the Windows Firewall via script/automation. Any thoughts?
Note: this is prior to joining the machines to the domain. If I manually clear the Local Security Policy from the MSC, then the registry hacks will work. netsh still won't work and I don't want to have to manually clear the policy for every imaged machine.